local-package

You can test local package changes without publishing by linking the local package directly into your consuming application's repository for immediate iteration and validation. This Skill streamlines that linking process.

The best way to manage local package links across repositories is to use straightforward commands that toggle local links, allowing you to quickly create links for testing and easily revert to published versions.

Yes, you can use this Skill to streamline local package development and testing workflows that involve tools like yalc and nx, ensuring safe environment management while satisfying build and validation requirements.

To revert from a local package link back to the published version, you use the package unlinking feature, which easily removes the local link and restores the consuming repository's dependency on the registry.

You need local package linking for multi-repository projects when package changes in a shared repository must be tested in a consuming app, allowing developers to rapidly iterate without publishing to a registry.