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

Feature: Move past Bower #234

Open
4 tasks
eddiemonge opened this issue Mar 15, 2016 · 3 comments
Open
4 tasks

Feature: Move past Bower #234

eddiemonge opened this issue Mar 15, 2016 · 3 comments

Comments

@eddiemonge
Copy link
Contributor

This is more of a todo/RFP to provide a way for wiredep to expand past Bower. Whether thats some property in npm or automatically determining them somehow from something like import {foo} from 'bar';

This would probably require a lot of work but I think it would benefit the community overall.

  • Support npm packages
  • Support component?? (I don't know why or if anyone still uses it)
  • Still support bower
  • Support passed in array/objects of dependencies (i.e. the whatever you want to use approach)
@eddiemonge
Copy link
Contributor Author

Some good discussion at #173 but keeping this one as the feature request issue to track this

@blowsie
Copy link

blowsie commented Oct 11, 2017

Its worth noting that bower are suggesting a bower > yarn migration so perhaps this feature should be focused on that.

@johnnyasantoss
Copy link

Hey!

I made a fork of this lib for people that are migrating from bower with bower-away.

You can find it https://github.com/johnnyasantoss/wiredep-away

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants