4 ms·
well for development that's a good idea. For production you don't want to have webpack serving anything, you want it compiled, right?
by d215 11y ago
well for development that's a good idea. For production you don't want to have webpack serving anything, you want it compiled, right?
- gitaarik 11y agoThat's what I do. Webpack compiles to the static/ dir and Django serves the static files in that dir. I don't know how/why you would do it otherwise.
- withjive 11y agoFor fast development iterations, running webpack's own web server is used for development. Where django would instead load a custom JS endpoint in development, and use the compiled file for production. Webpack static compile each time is just way to slow— I've seen it take 60+seconds to compile.