FIX: Includes version.cjs in .npmignore #311
Merged
Conversation
This file contains 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
…ublished package from functioning correctly.
ThaUnknown
approved these changes
Jun 14, 2024
webtorrent-bot
pushed a commit
that referenced
this pull request
Jun 14, 2024
## [5.1.2](v5.1.1...v5.1.2) (2024-06-14) ### Bug Fixes * include version.cjs in the .npmignore, which is preventing the published package from functioning correctly. ([#311](#311)) ([c3138e0](c3138e0))
|
🎉 This PR is included in version 5.1.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
What is the purpose of this pull request? (put an "X" next to item)
[ ] Documentation update
[x] Bug fix
[ ] New feature
[ ] Other, please explain:
What changes did you make? (Give an overview)
This PR adds an exclusion to
version.cjsin the.npmingore, which is currently excluding this file from the published package, preventing[email protected]from working whatsoever.Following this change,
npm packgenerates a package with all the required files and works as expected:Which issue (if any) does this pull request address?
Is there anything you'd like reviewers to focus on?