You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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!
The text was updated successfully, but these errors were encountered: