Skip to content
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

Fails when Bower is not globally installed. #11

Closed
rwjblue opened this issue Apr 4, 2015 · 1 comment · Fixed by #12
Closed

Fails when Bower is not globally installed. #11

rwjblue opened this issue Apr 4, 2015 · 1 comment · Fixed by #12

Comments

@rwjblue
Copy link
Member

rwjblue commented Apr 4, 2015

This might seem obvious, but if the bower command is not available in $PATH we throw an error.

Ember CLI bundles bower itself (to avoid just this problem on ember init and ember new), so we should be able to tap into its bower install.


Discovered this due to ember-cli integration failures on Ember CLI's Windows CI system. Example output:

     Running: node_modules\ember-cli\bin\ember try:testall
version: 0.2.2--af1623b89b

events.js:85
      throw er; // Unhandled 'error' event
            ^
Error: spawn bower ENOENT
    at exports._errnoException (util.js:746:11)
    at Process.ChildProcess._handle.onexit (child_process.js:1053:32)
    at child_process.js:1144:20
    at process._tickCallback (node.js:355:11)
@rwjblue
Copy link
Member Author

rwjblue commented Apr 4, 2015

I'm toying with a potential solution for this now...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant