companion-packages

What problem does it solve?

Working in the brepjs monorepo often leads to confusion about which package serves what purpose, why build or npm errors occur, how to order tasks correctly, and how to safely add or modify workspace packages without breaking the release pipeline or CI.

Core Features & Use Cases

• Full package map: Clear reference for all 9 monorepo packages and 2 apps, including their publish status, purpose, and tier (published satellite, source-shipped internal, private).
• Error troubleshooting: Step-by-step fixes for common issues like npm ETARGET errors, stale playground builds, missing WASM files, Dependabot alerts on wildcard dependencies, and failed manual publishes.
• Build and release guidance: Explicit build order for all common workflows (playground, full site, brepjs-cad) and clear rules for the release-please managed publish pipeline.
• New package checklist: Step-by-step guidance for adding new workspace packages, including tier selection, dependency setup, CI configuration, and release pipeline integration. Use case: If you are editing brepjs-bim and notice the playground is showing stale behavior, or npm ci fails with an ETARGET error after merging a leaf release PR, this skill gives you the exact root cause and fix.

Quick Start

Use the companion-packages skill to resolve the npm ETARGET error you are seeing after editing a brepjs workspace package and pushing a change.