Re: Proposal: FileSystemFinder and AppDirectoriesFinder shall serve unminimized assets in DEBUG mode

> On 25 Apr 2020, at 21:59, Jacob Rief wrote: > > So unless Django embraces npm in order to execute the > compile/compress/concatenate/uglify-steps, I don't see a lot of possibilities > other than referring to the processed, aka *.min.xyz file. Well, see the other thread

Re: Proposal: FileSystemFinder and AppDirectoriesFinder shall serve unminimized assets in DEBUG mode

On Friday, April 24, 2020 at 7:21:24 AM UTC+2, Carlton Gibson wrote: > > For instance if we were to include a compression step, you’d always just > reference the raw assets, these being processed, with source maps if we had > that, for production. > It certainly is the proper approach to refer

Re: Proposal: FileSystemFinder and AppDirectoriesFinder shall serve unminimized assets in DEBUG mode

It seems this thread ties in with the current discussion about static assets. For instance if we were to include a compression step, you’d always just reference the raw assets, these being processed, with source maps if we had that, for production. -- You received this message because you are

Re: Proposal: FileSystemFinder and AppDirectoriesFinder shall serve unminimized assets in DEBUG mode

Maybe we can move to always serving minimized assets with corresponding source maps? I was under the impression this is the "best practice" these days. On Thu, 23 Apr 2020 at 10:09, Jacob Rief wrote: > When specifying paths to assets like JavaScript files, but also CSS, the > Django