Open Russell-Jones-OxPhys opened 5 years ago
Hi! I will try to remove bower soon. I don't have too much to time to maintain the project, but I will try to do de effort.
Thanks!
I'm just playing with this, TBH, so not too committed to it, but at some point I'll have a look at https://github.com/epineda/django-yarn as an alternative to django-bower. Have you looked at it at all or do you have any thoughts on it's suitability as a replacement?
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?
Hi!
I'm thinking of removing all js and HTML files of schedule since most of the people use the model and the API.
I am starting using this app, I would like to use HTML/JS code, I don't think I need an API so far, I am also learning wepback, so maybe I can implement django-webpack in the future.
@robertpro that will be great!
@llazzaro I am understanding this app a little more and I see why you want to remove the HTML/JS files, I think now that's actually a good idea and I will be using the API only which works great with fullcalendar as a frontend, besides that I didn't knew how to implement webpack, I think is easier and is OK to add JS/CSS dependencies from the CDN (I might be wrong, I am just a python dev).
@llazzaro Maybe you could split it into django-scheduler-backend
and django-scheduler-frontend
?
Any updates on this?
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.