-
Notifications
You must be signed in to change notification settings - Fork 13
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
matchPrefix
in .bowerrc makes npm:name
in bower.json not work
#17
Comments
In fact I just realized by reading code that this can be turned on with another (undocumented) setting
Maybe it should default to |
The problem here would be that the prefix should be stripped for Any reason you're not simply doing |
Hi @jakub-g, I see two problems here:
And sorry for the delay, I was in vacation last two weeks ;) |
@mhofman @mjeanroy You raised good points about
In fact, why would we not want to strip To put you in the context, my use case is as follows: I started using bower-npm-resolver with just this is how it looks like now
The same can be achieved without configuring
If we wanted to cut on complexity, one more option to follow (a bit extreme) could for the resolver to throw an error when |
sounds good to me |
.bowerrc
bower.json
Run
bower install --verbose
Expected:
matchPrefix
in .bowerrcnpm:moment
syntax in bower.jsonActual:
The text was updated successfully, but these errors were encountered: