Closed tute closed 10 years ago
The package.json
has specifies that bower install
should be run after npm install. That doesn't make sense.
In your case, you can either install bower locally or just send a PR to modify the package.json file
and remove this bower command. I'll try doing that myself when I get home. If you have some time, a patch is welcome :)
Which package.json
? Happy to help, but I'll need a little more guidance. Thanks for your quick response!
This line: https://github.com/kurko/ember-sync/blob/master/package.json#L18 Whenever you run npm install ember-sync
, it'll run bower install
. If you send a patch removing that line, it should be fixed.
I'll only have time to look into it myself tomorrow evening.
closed from that PR and when npm gets updated
The package.json has specifies that bower install should be run after npm install. That doesn't make sense.
@kurko, this is unrelated to the PR, but I arrived here from a Google search for the exact error message in another NPM package. For posterity, why doesn't it make sense?
@john-kurkowski The error message is simply saying the bower
is not installed globally on your machine. You need to install it with npm install -g bower
and the error should go away.
My case is the same as the original issue's:
./node_modules/bower/bin/bower: No such file or directory
Some other package is actually looking for bundled Bower, not global.
Regardless I'm not curious about how to fix the error. I'm curious why @kurko thought the npm install
+ bower install
sequence doesn't make sense as a postinstall
hook. It's the sequence ember-cli Getting Started requires, for example. Albeit they don't mention postinstall
.
Thank you for your work!