This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of postinstall-build.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
The postinstall-build script accepts a new flag --only-as-dependency. When present, it will skip building when you do an npm install in the package's own directory (for development). The build will only occur if the package is being installed as a dependency (and the specified build artifact is missing). Fixes #13.
In some cases, npm itself can end up being installed somewhere in your dependency tree (for example, older versions of ember-cli install it), resulting in its npm script shadowing the version you're actually using. This means any npm run ... or npm install ... you have in your lifecycle scripts (like those from postinstall-build) may end up running an incompatible version of npm.
To solve this, postinstall-build will now execute $npm_execpath instead of just npm (when the user agent is npm). If you're concerned about this, it's also a good idea to use the --script option to specify your build command instead of npm run ... – that way, postinstall-build can fix up that npm reference for you.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Hello lovely humans,
postinstall-build just published its new version 3.0.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of postinstall-build. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
The
postinstall-build
script accepts a new flag--only-as-dependency
. When present, it will skip building when you do annpm install
in the package's own directory (for development). The build will only occur if the package is being installed as a dependency (and the specified build artifact is missing). Fixes #13.In some cases, npm itself can end up being installed somewhere in your dependency tree (for example, older versions of
ember-cli
install it), resulting in itsnpm
script shadowing the version you're actually using. This means anynpm run ...
ornpm install ...
you have in your lifecycle scripts (like those frompostinstall-build
) may end up running an incompatible version of npm.To solve this,
postinstall-build
will now execute$npm_execpath
instead of justnpm
(when the user agent is npm). If you're concerned about this, it's also a good idea to use the--script
option to specify your build command instead ofnpm run ...
– that way,postinstall-build
can fix up thatnpm
reference for you.The new version differs by 7 commits .
057e70c
3.0.0
f6dba9b
Use npm_execpath and add --only-as-dependency flag (#14)
aba4e9f
Add note about Yarn and private registries
33f376a
Test npm@4.0 and allow npm@4 to fail on AppVeyor
a6f470f
Force test with npm 4.0.x since 4.1.x and above are broken, allow v4 to fail
a48a3ea
Add note about npm 4.1.x bug
4720bdc
Add npm v4 to build matrix (#10)
See the full diff.
Screencast
Try it today. Free for private repositories during beta.