Convert one local dependency in your project to a Pkglink. Notice how you can edit the source and see changes instantly. Then, expand to cross-project links. Finally, use the lockfile to ensure your CI pipeline is deterministic.
cd apps/web pkglink add ../packages/ui --as @myorg/ui Now @myorg/ui is linked directly. Change a button component in packages/ui and apps/web hot-reloads instantly. You forked a critical library ( lodash-fixed ) on GitHub. Instead of waiting for a PR merge: Pkglinks
The tools are emerging, the standard is solidifying, and the benefits are undeniable. Don't get left behind in dependency hell – embrace the clarity of . Ready to dive deeper? Check out the official Pkglinks specification or try the pkglinks CLI on your next side project. Your future self (and your disk space) will thank you. Convert one local dependency in your project to a Pkglink
But what exactly are Pkglinks? How do they differ from traditional symlinks or monorepos? And why should you integrate them into your workflow today? Finally, use the lockfile to ensure your CI