Open norrishung opened 9 years ago
Do we have enough JS to justify this right now?
Not very much JS but isn't this just something you should do as a good practice no matter how much js/css you have? Definitely not a high priority but are there downsides to doing this?
Main downside I can think of is that it introduces a build step where one might not be needed. I’m a fan of serving JS & CSS unmodified until they get too big, because I think it’s easier to reason about when debugging in-browser.
One of the positives to going the route of #531 is that JS can be compiled with sourcemaps that ease debugging and separate modules at the same time. A very convenient time-saver all around.
Using something like this?
http://flask-assets.readthedocs.org/en/latest/
I'm curious what the best way to do this is if you have different javascript modules across different pages.