10 Matching Annotations
- Dec 2019
-
debuggable.com debuggable.com
-
The url also contains an optional refspec (#v0.0.1) that tells npm which branch, commit, or in this case tag you want to have checked out.
-
-
github.com github.com
-
"neutrino-patch": "git+https://github.com/davidje13/neutrino-patch#semver:^1.0.1"
-
-
github.com github.com
-
npm install --save git+https://github.com/davidje13/neutrino-patch#semver:^1.0.1
-
- Aug 2019
-
stackoverflow.com stackoverflow.com
-
I found adding a "prepare": "npm run build" to scripts fixed all my problems.
-
Update the package.json in your forked repo to add a postinstall element to scripts. In here, run whatever you need to get the compiled output (Preferred).
-
-
-
instead of prepublish, you'll need to use prepare, but this is otherwise as you'd expect.
-
-
-
docs.npmjs.com docs.npmjs.com
-
prepare: Run both BEFORE the package is packed and published, on local npm install without any arguments, and when installing git dependencies
-
-
stackoverflow.com stackoverflow.com
-
This is because it's not bundled at all, while the package expects an prebuilt version existing in dist.
-