Hi Ashik,
Thanks for your proposal that I find revelant because there needs to be a
new version of staticfiles.
Supporting NPM, one way or another, is the main way to enjoy the same
development workflow with frontend code as with pip. For me it would make
sense to support it, one way or another. {% block extra_js %} overrides
kind of works, but overriding frontend code delivered by an app is far from
convenient
<https://github.com/yourlabs/django-autocomplete-light/issues/1016#issuecomment-478798707>
when it involves copying a minified script from an app into an override
static dir and patching that minified code. Also dealing with {{ form.media
}} definitely doesn't cut it, ie. when if you load jquery in your base.html
and a form media also contains a jquery, this means we load the same script
twice, and that also causes issues ie. with plugin loading. So it doesn't
look like anybody would deny that static file management in Django needs an
upgrade.
However, the suggestion to contribute to other existing third party apps is
valid. Before contributing to Django you need to study the current state of
the art in the Django ecosystem, that lives in external projects.
Contribute to those, see why you believe they don't cut it, and make a
write up the existing django static file apps ecosystem, that would be a
great start.
Have a great day
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/CAC6Op18N1O6hFnwgrmnw28c_-warB-KMGO68S572xz--9SGGaQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
