fix(hub): ship dist/ in published tarball#27
Merged
Conversation
Without a prepack hook, npm pack never builds dist/ — so 0.5.0 and 0.5.1 published as empty tarballs (LICENSE.md + package.json only, 2.4 KB).
✅ Deploy Preview for devfra ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
0.5.0 and 0.5.1 published empty tarballs (LICENSE.md + package.json only, 2.4 KB) because the package had no
prepackhook to builddist/before npm ran, so consumers couldn't resolve any of the entry points in the exports map. This adds the samepnpm run buildprepack that@devframes/nuxtalready uses, so the next release ships the fulldist/tree. Broken 0.5.0 and 0.5.1 will neednpm deprecateafter the follow-up release goes out.This PR was created with the help of an agent.