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

use of main-bower-files after using bower-away #167

Open
tansaku opened this issue Nov 6, 2017 · 4 comments
Open

use of main-bower-files after using bower-away #167

tansaku opened this issue Nov 6, 2017 · 4 comments

Comments

@tansaku
Copy link

tansaku commented Nov 6, 2017

Has anyone tried to continue using main-bower-files after using bower-away to switch to yarn?

@ck86
Copy link
Owner

ck86 commented Nov 7, 2017

I don't use bower since ages anymore, because of webpack / code splitting / yarn / es6 modules / etc. ;)
So personally I wouldn't recommend using it anymore. This is also the reason why I don't really update this project.

@tansaku
Copy link
Author

tansaku commented Nov 7, 2017

@ck86 we're trying to shift away from bower, but bower-away doesn't take into account the way gulp uses main-bower-files. We've rolled our own hard coded solution, but wondered if there was some existing gulp related package that could pick out the set of bower_components that bower_away moves to package.json ...?

@tansaku
Copy link
Author

tansaku commented Nov 7, 2017

more details in sheerun/bower-away#13

@ck86
Copy link
Owner

ck86 commented Nov 7, 2017

If I understand you correctly, you could try to override the paths option to tell main-bower-files to search the dependencies in node_modules. Have a look at: https://github.com/ck86/main-bower-files#paths

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

2 participants