Write the dependency tree (component deps) into package.json — merge-safe - molecule-publish

Overview Files Skills Discover Packages Releases Dependencies Issues12 Breadcrumbs Pull Requests Activity

Open general

Write the dependency tree (component deps) into package.json — merge-safe

barrett-land · 11d ago

Part of #1.

APM lists a board/molecule's components from package.json.dependencies (its board_deps reads them and expands one hop, so deps can live directly on the page — no separate library page needed). Molecule/board pages currently have no deps, so APM shows an empty component list.

Requirements

Map the design's schematic/BOM parts → wiki component slugs (MPN → slug). Reuse the mapping logic in adom/adom-project-manager → skills/publish-board/kicad_board_bundle.py (note its Value-fallback caveat: value-named symbols like R_4.3K_0402 are NOT real component slugs — resolve the real MPN).
Write them (owner-qualified, e.g. adom/<slug>) into dependencies.
Merge, never overwrite — preserve the existing component block, hero, tags, model_3d_path, version. Bump version, re-publish (the dep GRAPH comes from pkg publish, not repo push).
Verify each component page exists; publish/flag any missing ones.

Acceptance

Opening the board/molecule in APM lists its components, resolved from the deps.
The molecule's component/hero/model_3d_path are intact after the dep write.

1 Reply

Drew Owens · 6d ago

Built and published in adom/[email protected] + adom/[email protected]: board shape (plain step2glb convert, tag board, no anchoring gates), unified .glb 3D for both shapes, render/ stage via adom-project-manager --render-board (live-verified on taprite-solonoid-wiretest: render/ pushed, 3 files; EAGLE sources skip gracefully), and the merge-safe dependency-write procedure incl. the Value-fallback caveat and the pkg-install side-effect note. #130 (deprecate publish-board + backfill) intentionally left to Barrett - Drew does not want us touching his data.