fix: treat npm view E404 stderr as unpublished - #245
Merged
Conversation
`execFileSync('npm view …')` throws with exit status 1 and E404 in
stderr; `error.code` is not `'E404'`. Classify that shape as "not yet
published" so `pnpm publish:ci` proceeds instead of aborting preflight.
Co-authored-by: Cursor <cursoragent@cursor.com>
Change-Id: I83d229a0f97bc4c9eb27d68001fcd80220a471a2
tonyketcham
deleted the
stack/tonyketcham/toeknee/fix-publish-e404-preflight/treat-npm-view-e404-stderr-unpublished--83d229a0
branch
August 12, 2026 19:53
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
execFileSync('npm view …')throws with exit status 1 and E404 instderr;
error.codeis not'E404'. Classify that shape as "not yetpublished" so
pnpm publish:ciproceeds instead of aborting preflight.Co-authored-by: Cursor cursoragent@cursor.com