question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

question: Uncaught TypeError: __webpack_require__(...) is not a function

See original GitHub issue

i’ve recently started experiencing this issue, where i will start up webpack as usual via npm run dev, where dev is defined in package.json as:

"dev": "webpack-dev-server --config webpack/webpack.dev.config.js --progress --colors --hot --inline",

then i’ll hit it in the browser with localhost:8080 and everything will be fine, until… i change a file in the app folder and 💥

Uncaught TypeError: __webpack_require__(...) is not a function
screen shot 2016-01-14 at 7 42 40 pm

ironically i first started seeing this when i was trying to upgrade to babel-6, and i came across this stack-overflow post, so i thought i hit paydirt, and tried this which didn’t help.

i then returned back to babel-5, and the issue was still there, so now i’m kind of flustered, any ideas appreciated!

here is a reference to my entire project if it helps

Issue Analytics

  • State:closed
  • Created 8 years ago
  • Comments:10 (2 by maintainers)

github_iconTop GitHub Comments

3reactions
jantimoncommented, Jan 19, 2016

Thanks @sokra for fixing this. I will release html-webpack-plugin 2.6.4 soon 👍

1reaction
ashutoshkushawahacommented, May 23, 2018

ERROR TypeError: webpack_require.i(…) is not a function at NgDropdownPanelComponent.ngOnInit. i am getting this error when i use @ng-select/ng-select for select2 . please help me.

Read more comments on GitHub >

github_iconTop Results From Across the Web

TypeError: __webpack_require__.i(...) is not a function
This error can arise if you try to import something from an existing npm package (in node_modules ) but the imported thing doesn't...
Read more >
TypeError: __webpack_require__(...) is not a function #9379
is not a function If the current behavior is a bug, please provide the steps to ... webpack.config.js const path = require('path'); ...
Read more >
__webpack_require__ is not a function - You.com | The ...
This error can arise if you try to import something from an existing npm package (in node_modules ) but the imported thing doesn't...
Read more >
JavaScript: Uncaught TypeError: n is not a function
This error occurs if you try to execute a function that is not initialized or is not initialized correctly. This means that the...
Read more >
TypeError: require(...) is not a function in Node.js | bobbyhadz
To solve the "TypeError: require(...) is not a function", make sure to place a semicolon between your require call and an immediately invoked...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found