We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This might seem obvious, but if the bower command is not available in $PATH we throw an error.
bower
$PATH
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.
ember init
ember new
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)
The text was updated successfully, but these errors were encountered:
I'm toying with a potential solution for this now...
Sorry, something went wrong.
ember
Mention engines so no one else gets caught by ember-cli#11
db359e5
Successfully merging a pull request may close this issue.
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 onember init
andember new
), so we should be able to tap into itsbower
install.Discovered this due to ember-cli integration failures on Ember CLI's Windows CI system. Example output:
The text was updated successfully, but these errors were encountered: