Bug 1693297 - Copy README.md on prepublish #77
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
If the README.md is not in the glean package folder, it will not be included in the final package and as a consequence will not show up on the package npm page.
brizental
commented
Feb 17, 2021
| @@ -21,7 +21,8 @@ | |||
| "fix": "eslint . --ext .ts,.js,.json --fix", | |||
| "build": "webpack --config webpack.config.js --mode production", | |||
| "dev": "webpack --watch --config webpack.config.js --mode development --devtool inline-source-map", | |||
| "prepare": "npm run build" | |||
| "prepublishOnly": "cp ../README.md ./README.md && npm run build", | |||
There was a problem hiding this comment.
Changed to prepublishOnly becase prepare also ran on npm install and that was annoying.
Dexterp37
approved these changes
Feb 17, 2021
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.
If the README.md is not in the glean package folder, it will not be included in the final package and as a consequence will not show up on the package npm page.