prepublish lifecycle script has been deprecated in npm@^4 #243
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.
See http://blog.lholmquist.org/npm-prepublish-changes/
Long story short, when using npm4+ and docpress/docpress-base, it wont build using
docpress build
if you are using a git repository as your package source instead of npm, even though its the exact same version.The reason was there is no
cache
dir being build fordocpress-base
if the npm package was included this way (even if its the exact same package as the one on npm)The solution I found was to use the new script lifecycle commands
prepublishOnly
andprepare
.Replication
Prerequsites
Steps
npm
docpress
vianpm
docpress serve
to test if its workingdocpress serve Docpress starting development - ^C to exit 236ms first build ✓ on livereload ✓ on http://localhost:3000 Running
package-lock.json
ornpm-shrinkwrap.json
and replacewith:
docpress serve
again to see if it works