xnpm upstream

Close the loop with
upstream packages.

Change requests live in docs. Fixes ship. Consumers never hear about them. Workarounds stay forever. xnpm upstream turns that scattered process into a tracked lifecycle.

The lifecycle

From change request
to verified fix.

xnpm upstream connects a documented change request in your consumer repo to the upstream package fix — and closes the loop with verification proof.

  • 1
    Write the change requestCR or FR documented in the consumer repo as markdown
  • 2
    Submit upstreamxnpm opens a structured issue on the upstream package repo
  • 3
    Owner ships a fixNew npm version published by the upstream package owner
  • 4
    Pull the fix versionConsumer lockfile updated to the exact fixed version
  • 5
    Verify and closeTests run against original acceptance criteria; verification comment posted as proof
Upstream fixes become traceable instead of scattered.
⚠ Available now as @x12i/xnpm-plugin-upstream — bundled in vNext.
full lifecycle
# 1. submit the change request $ xnpm upstream submit --id CR-FUNCX-2 ✓ Issue #147 opened on upstream repo # 2. check status $ xnpm upstream status --id CR-FUNCX-2 ✓ Fix shipped: @upstream/pkg@3.1.2 # 3. pull the fix version $ xnpm upstream pull-fix --id CR-FUNCX-2 ✓ Lockfile updated to 3.1.2 # 4. verify and close $ xnpm upstream verify --id CR-FUNCX-2 --comment ✓ Tests pass with 3.1.2 ✓ Verification comment on #147 ✓ Issue closed

CLI surface

All upstream commands.

xnpm upstream
xnpm upstream submit --id <id>Open a structured issue on the upstream repo
xnpm upstream status --id <id>Check whether a fix has shipped
xnpm upstream pull-fix --id <id>Update lockfile to the exact fixed version
xnpm upstream verify --id <id>Run tests against original acceptance criteria
xnpm upstream verify --id <id> --commentPost verification result as a comment on the upstream issue
Install upstream plugin
npm install -g @x12i/xnpm-plugin-upstreamCurrent standalone package
npm install -g @x12i/npmBundled in vNext — no extra install needed