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

Dependency resolving using a custom bower resolver #247

Open
franknarf8 opened this issue Jul 7, 2016 · 0 comments
Open

Dependency resolving using a custom bower resolver #247

franknarf8 opened this issue Jul 7, 2016 · 0 comments

Comments

@franknarf8
Copy link

Hello,

We have stumbled upon a problem recently. We started using a custom bower resolver (https://bower.io/docs/pluggable-resolvers/). Those resolvers use the string in the bower.json (dev)dependencies section to figure out which resolver to use (e.g. The svn resolver will be used if the dependency package name is prefixed by 'svn://')

Unfortunately, at this time, wiredep resolves it's stuff using the dependencies full names in the bower.json file. (e.g. It is going to look for the 'svn://dependency_name' folder during its order resolution)

Could it be possible to strip everything before '://' (it looks like to be a standard for the custom resolvers) for wiredep's resolution? Would this have any other implications?

Thanks!

  • Frank
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

No branches or pull requests

1 participant