I just compared your package.json to mine, and perhaps this has to do with running: npm install --save-dev webpack webpack-cli (without specifing versions) installed:
"webpack": "^4.44.2",
"webpack-cli": "^3.3.12"
several months ago, but running it today installed
I just tested this and yes, it looks like with the new versions of webpack and webpack-cli, the use of publicPath is required to make Django serve the bundle at the correct url. I've updated the article and the GitHub repo. Thanks for pointing this out!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi Zack, Great Post! I ended up having to add
to the config passed to the BundleTracker constructor in my webpack.config.js
by default my webstat-stats.json was being generated with:
which got prepended as
I just compared your package.json to mine, and perhaps this has to do with running:
npm install --save-dev webpack webpack-cli
(without specifing versions) installed:several months ago, but running it today installed
? Just a guess
I just tested this and yes, it looks like with the new versions of
webpack
andwebpack-cli
, the use ofpublicPath
is required to make Django serve the bundle at the correct url. I've updated the article and the GitHub repo. Thanks for pointing this out!