Repository navigation
Build src/ on git-install via a prepare script - #94
Merged
Merged
Conversation
prepublishOnly only runs on npm publish, so installing this package straight from git (e.g. a consumer pinning a commit before a release) left it with no src/ and an unresolvable main/style. Add a prepare script (same steps) so the build runs on git-install too, and gitignore the generated src/ and *.bak.
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.
prepublishOnlyonly runs onnpm publish, so installing this package straight from git — e.g. a consumer pinning a specific commit before a release is cut — leaves it with nosrc/, andmain/style(which point atsrc/…) can't resolve.Add a
preparescript (same two steps asprepublishOnly:prepare_src+prepare_import) so the build also runs on git-install and localnpm install, and gitignore the generatedsrc/and*.bakso they're never committed.No change to published releases —
prepublishOnlystill runs on publish exactly as before.