Build on prepublishOnly so dist is never stale at publish#26
Open
kashishhora wants to merge 2 commits into
Open
Build on prepublishOnly so dist is never stale at publish#26kashishhora wants to merge 2 commits into
kashishhora wants to merge 2 commits into
Conversation
naji247
approved these changes
Jul 3, 2026
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
2 participants
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
The package publishes
files: ["dist"]but had no build step wired into the publish lifecycle, sonpm publishwould ship whatever happened to be indist/(stale or missing) unless you remembered topnpm buildfirst.Adds
"prepublishOnly": "pnpm build"sonpm publishalways rebuildsdist/first.Test plan
npm run prepublishOnlybuildsdist/successfullypnpm lintclean