Avoid issue where ember init
stalls on fresh system
#1805
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is an issue where (on a fresh system, which has never run bower before), the bower 'opt-in analytics prompt' will show for a sliver of time (since npm refreshes the cli output with a spinning pipe (
\ | / -
). This causes the initialember init
to stall indefinitely.This patch opts out of analytics via .bowerrc, to circumvent the above issue.
More on bower analytics opt-in:
bower/bower#1162