The webpack documentation says, if you don't know publicPath when compiling you can specify __webpack_public_path__ in your entry point. __webpack_public_path__ becomes __webpack_require__.p in the webpack bundle. It appears that after hot reloading there are at least two copies of the function __webpack_require__ since the p property is only set on one of them. My hot reload is failing because whatever copy of __webpack_require__ it's using to hot reload doesn't have p set to the new value. If I set publicPath in webpack.config.js the reload works fine.
Does this sound correct? Thanks for any guidance!
The webpack documentation says, if you don't know
publicPathwhen compiling you can specify__webpack_public_path__in your entry point.__webpack_public_path__becomes__webpack_require__.pin the webpack bundle. It appears that after hot reloading there are at least two copies of the function__webpack_require__since thepproperty is only set on one of them. My hot reload is failing because whatever copy of__webpack_require__it's using to hot reload doesn't havepset to the new value. If I setpublicPathinwebpack.config.jsthe reload works fine.Does this sound correct? Thanks for any guidance!