fix: strip dev scripts before publish to fix npx install#17
Merged
Conversation
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
1 participant
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.
Summary
npx webttyfails because the npm registry manifest for published versions containspreinstall: bun scripts/check-pkg-manager.ts. When users install via npx, npm runs this script, which fails becausescripts/check-pkg-manager.tsdoesn't exist in the installed package.Root cause:
prepackstrips scripts from the tarball'spackage.json, but npm uploads the registry manifest frompackage.jsonbeforeprepackruns. So the tarball is clean but the registry metadata still has all scripts.Fix: Explicitly run
clean-pkg-scripts.ts stripbefore semantic-release in the release workflow, so the manifest npm sends to the registry is also clean.