local-package
Use Clipboard's internal CLI to link and unlink @clipboard-health packages across repositories for local development. Use when testing local package changes, linking @clipboard-health packages between repos, or using the cbh CLI local-package command.
Installation
Suivez les instructions du dépôt pour votre agent. Consultez les fichiers et dépendances avant l’installation.
Voir la source ↗GuidesInstructions
Local Package Development
Use Clipboard's internal CLI (@clipboard-health/cli) to test package changes across repositories without publishing. The cbh local-package command wraps yalc to simplify linking packages between sibling repositories.
Prerequisites
See the CLI README for setup instructions.
Commands
Link packages
From the consuming repository, link packages from sibling repos:
cbh local-package link --packages <package-names...>
Example:
cbh local-package link --packages ui-theme ui-components
This will:
- Find the package in sibling
packages/*directories - Build the package with nx
- Push the built package to yalc
- Update your
package.jsonto use the yalc version
Unlink packages
After testing, restore the published package versions:
cbh local-package unlink --packages <package-names...>
Example:
cbh local-package unlink --packages ui-theme ui-components
Workflow Example
To test changes to ui-theme in cbh-mobile-app:
-
Make changes to
ui-themeincbh-core -
From
cbh-mobile-approot, run:cbh local-package link --packages ui-theme -
Test your changes in
cbh-mobile-app -
When done, unlink:
cbh local-package unlink --packages ui-theme
Troubleshooting
-
Package not found: Ensure the package exists in a sibling repo's
packages/directory - Build fails: The package must have a valid nx build target
-
Changes not reflected: Run
npm installafter linking to pull in the yalc version
Exemples
Consultez les exemples du dépôt source.
Voir la source ↗Historique source
- Date d’indexation
- 2026-01-20
- Mise à jour de l’index
- 2026-01-28
- Branch
- main
Les dates concernent ce répertoire. Consultez le dépôt pour l’historique du code.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!