__webpack_require__(...) is not a function

[mikechabot]

Very recently I started experiencing the error below on an otherwise stable application. The application loads successfully, however after the very first hot reload, the error is thrown. This just started occurring, however no code was altered

This is reproducible here: https://github.com/mikechabot/webpack-dev-server-error
Also reported here: webpack/webpack#1890

Uncaught TypeError: __webpack_require__(...) is not a function
(anonymous function) @ punycode.js:530
(anonymous function) @ bundle.js:569
__webpack_require__ @ bundle.js:521
fn @ bundle.js:76
(anonymous function) @ url.js:22
(anonymous function) @ bundle.js:563
__webpack_require__ @ bundle.js:521
fn @ bundle.js:76
(anonymous function) @ client:1
(anonymous function) @ client:98
(anonymous function) @ bundle.js:557
__webpack_require__ @ bundle.js:521
fn @ bundle.js:76
(anonymous function) @ multi_main:1
(anonymous function) @ bundle.js:551
__webpack_require__ @ bundle.js:521
(anonymous function) @ bundle.js:544
(anonymous function) @ bundle.js:547

[gatorcse]

I'm also getting this

[mikechabot]

See: webpack/webpack#1890
Fix: jantimon/html-webpack-plugin#179

[samarhaider]

Changing Echo.channel('xyz') to window.Echo.channel('xyz') should fix that.

[agarwalsween]

@gatorcse
Hello Sir,
Still, Getting same error ,Please help me asap.

[hmeerlo]

This issue still happens for me, only not on a hot reload. It happens at the first page load immediately. But the same stack (with punycode and url). My html-webpack-plugin is up-to-date (2.30.1). Any idea's?

[Dakuan]

@hmeerlo ditto, I've also created a stack overflow issue: https://stackoverflow.com/questions/48700978/webpack-dll-plugin-not-running

[m-farahmand]

i'm getting this too.
I run webpack-dev-server inside gulp task and after stopping task my server has not been kill from window taskmanager, when I end all node process from memory and re-Run my task this error disappears.
I think maybe my context be useful for you

[fvonellerts]

I had this problem when using new webpack.ExtendedAPIPlugin() in webpack.config.js.
I used it to extract the webpack hash into the application - removing the plugin for HMR mode fixed the error.