The gap

What npm doesn't do
for you.

Every time you release, you're manually handling things npm never promised to handle.

xnpm wraps that whole workflow into safe, repeatable commands. It does not replace npm. It makes npm workflows automation-ready.

Before vs after

What a real multi-package
release looks like.

Without xnpm

# package 1 of 4 cd core && npm run build npm test && npm version minor npm publish # package 2 of 4 cd ../utils npm install @scope/core@latest npm run build && npm test npm version minor && npm publish # ... repeat for api, cli ... git add . && git commit && git push
  • One missed package
  • Wrong dependency order
  • Forgotten test run
  • Leaked .env in publish
  • Broken downstream consumer

With xnpm

$ xnpm --full-flow ✓ Found 4 packages ✓ Dependency graph resolved ✓ Installed in order ✓ Built in order ✓ Tests passed ✓ No sensitive files detected ✓ Published: core, utils, api, cli ✓ Git pushed Done. Exit 0.
One command. Correct order. Every time.