Make sure to have your package on npm first.

[wKovacs64]

Hey all,

Any idea why pkg-pr-new publish --compact would suddenly start failing to find the package on npm (or how to troubleshoot)? It's there, and it's been working for quite some time. 🤔

Run npx --yes pkg-pr-new publish --compact
  
Error:  pkg-pr-new cannot resolve hibp from npm. --compact flag depends on the package being available in npm.
Make sure to have your package on npm first.
  Make sure to have your package on npm first.
  at verifyCompactMode (/home/runner/.npm/_npx/e8f433c388b218fc/node_modules/pkg-pr-new/dist/index.js:3700:11)
  at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
  at async Object.run (/home/runner/.npm/_npx/e8f433c388b218fc/node_modules/pkg-pr-new/dist/index.js:3357:15)
  at async runCommand (/home/runner/.npm/_npx/e8f433c388b218fc/node_modules/pkg-pr-new/dist/index.js:2939:16)
  at async runCommand (/home/runner/.npm/_npx/e8f433c388b218fc/node_modules/pkg-pr-new/dist/index.js:2930:11)
  at async runMain (/home/runner/.npm/_npx/e8f433c388b218fc/node_modules/pkg-pr-new/dist/index.js:3066:7) 
Error:  pkg-pr-new cannot resolve hibp from npm. --compact flag depends on the package being available in npm.
Make sure to have your package on npm first.
Error: Process completed with exit code 1.

Thanks.

[wKovacs64]

Seems to have resolved itself after a few days/weeks? 🤷‍♂️

[wKovacs64]

And it's back. 😅 Different repo this time. Intermittent, it seems.

[AmirSa12]

Hey @wKovacs64 ! hope you are doing well! this is weird...
I had a look at the previous repo back then, I didn't find anything abnormal.
I'll have a look again, could you also share the repo you are facing the issue on rn?

[wKovacs64]

Hey @AmirSa12 thanks for the response! It's happening on https://github.com/wKovacs64/pwned this time. 🤷‍♂️

[JReinhold]

FWIW I'm all of a sudden seeing the same issue with @storybook/addon-mcp. Curiously, the other package in the monorepo, @storybook/mcp seems to work fine.

This started happening when I released @storybook/addon-mcp@0.1.4 promoting from @storybook/addon-mcp@0.1.4-next.2. Although I have no idea if it's a coincidence or not.

Last succesful run: https://github.com/storybookjs/mcp/actions/runs/19550546444
First failing run: https://github.com/storybookjs/mcp/actions/runs/19550750679