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

proposal: migrate from bower to yarn / webpack #182

Open
shaunc opened this issue Dec 27, 2018 · 1 comment
Open

proposal: migrate from bower to yarn / webpack #182

shaunc opened this issue Dec 27, 2018 · 1 comment

Comments

@shaunc
Copy link

@shaunc shaunc commented Dec 27, 2018

I haven't used bower for a number of years; checking out their site, I now see: "...psst! While Bower is maintained, we recommend using Yarn and Webpack or Parcel for front-end projects read how to migrate!"

If this project is meant to be viable going forward, I propose migrating from bower to npm or yarn and webpack.

This would certainly support the main use case. I am interested in incorporating as a library, and the current lack of a package.json means I need to hard-fork, which is unfortunate.

@stej
Copy link

@stej stej commented Feb 5, 2019

Even when installing, there is a warning:

[51]: npm install -g bower
npm WARN deprecated bower@1.8.8: We don't recommend using Bower for new projects. Please consider Yarn and Webpack or Parcel. You can read how to migrate legacy project here: https://bower.io/blog/2017/how-to-migrate-away-from-bower/
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.