-
-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bower install necessary in postinstall? #6
Comments
There is a known problem that installing ember-cli/npm with sudo, information found here The solution to your problem would be to set up node/npm so they don't need to run with sudo. We can't just remove the bower install, this project would not install successfully so it is necessary to have it. If you have another solution I'd be happy to look at it. Also, the reason it was removed from ember-cli was that the init command already does it, relevant code found here |
ok thank you for your quick answer! |
@jakecraige this postInstall is causing all kinds of annoying output. Can you move it to a pre-publish hook instead? This would also improve reliability of installing this addon. related: ember-cli/ember-cli#1746 |
@stefanpenner - how would prepublish help? |
Also, the point is to not have the npm package contain the vendored code. |
I have to run npm install in a ember-cli project as root. A bower install with root rights causes some trouble. I'd rather call bower install myself with
bower install --allow-root --config.interactive=false
Note that ember-cli once did the same and removed bower install in postinstall: ember-cli/ember-cli@01c16b4
Here is a short snippet of what npm screams at me when ember-cli-qunit runs bower install:
...
The text was updated successfully, but these errors were encountered: