-
Notifications
You must be signed in to change notification settings - Fork 143
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
Before erroring, check .bowerrc for folder location #66
Comments
Yes! I've been meaning to do this, but haven't been able to get around to it. Would you like to send in a PR? |
@thataustin I got antsy and tried to implement. Feel free to review and leave any thoughts. (#67) |
Merged 👍 |
@stephenplusplus looks great! I had implemented almost the same thing, but didn't get far enough in the tests to commit. The only thing I might add would be another console.log explaining where all you checked for the bower folder before you decided that you couldn't find it to make it easier for the user to fix in a case like that. But you did add it to the docs (:thumbsup:), so not too concerned if you don't :) |
When no directory was explicitly specified and the bower_components folder can't be found in it's usual place, I think the .bowerrc file should be checked for a folder location. If it's not specified there, the error can proceed as per normal.
The text was updated successfully, but these errors were encountered: