Pkglinks -

📦 shared-lib (local) -> /absolute/path/to/my-shared-lib Status: linked, hash: a1b2c3... Import/require as usual. The package manager resolves shared-lib to its linked location. Step 5: Unlink or Promote Once you publish shared-lib v1.0 to a registry:

pkglinks unlink shared-lib pkglinks add shared-lib@^1.0 --from-registry npm | Feature | npm/yarn symlink | Git submodule | Monorepo | Pkglinks | |--------|----------------|---------------|----------|----------------| | Cross-project dev | ✅ (via npm link ) | ❌ | ✅ | ✅ | | Version awareness | ❌ | ✅ | ❌ | ✅ | | Lockfile support | ❌ | ❌ | ✅ | ✅ | | Works across languages | ❌ | ❌ | ❌ | ✅ | | Automatic cleanup | ❌ | ✅ | ✅ | ✅ | | Registry fallback | ✅ | ❌ | ✅ | ✅ | Pkglinks

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. Step 5: Unlink or Promote Once you publish shared-lib v1

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