Adding New npm/yarn Packages

racletteJS uses a dual-layer package model: local tooling dependencies and runtime service dependencies.

Two Files, Two Purposes

• package.json: local workspace dependencies for IDE/tooling and project-level packages.
• packages.json: service-targeted runtime dependency declarations (frontend, backend, optional workbench).

Why This Is Needed

Container runtime dependencies are installed per service and should stay explicit.
A plain yarn add only updates local workspace dependencies and does not model service-targeted runtime installation by itself.

Recommended Workflow

1. Add runtime dependencies via yarn add-package <target> <package>.
2. racletteJS updates local package context and service runtime manifests.
3. Generated service package.json files in .raclette/<service>/ are used in containers.

Runtime Installation Behavior

• Containers install dependencies from generated service package manifests.
• node_modules live in container volumes per service.
• Lock files are seeded and updated through raclette workflows.

Practical Guidance

• Prefer add-package for runtime deps.
• Avoid manual edits to generated package files inside .raclette.