Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Bower is deprecated and suggests moving to Yarn and Webpack or Parcel
See original GitHub issue$ npm install 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/
the link explains how to use bower-away https://github.com/sheerun/bower-away to create a dependencies list for Yarn (packages.json) as part of migrating to it.
Or maybe this is just a case of updating docs? Or shouldn’t be fixed for some reason? I’m only very vaguely familiar with the nodejs ecosystem, but as I couldn’t find a bug on this in the project’s tracker, I thought I ought to file one.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hi!
I’m thinking of removing all js and HTML files of schedule since most of the people use the model and the API.
Why don’t we just use webpack instead? I have been using django-scheduler without calendar-display features so far, cause I didn’t want to install bower. And everyone with a JS frontend uses webpack, if I’m not mistaken?