Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

__webpack_require__.e is not a function #10104

Closed
ArgonAlex opened this issue Dec 10, 2019 · 0 comments
Closed

__webpack_require__.e is not a function #10104

ArgonAlex opened this issue Dec 10, 2019 · 0 comments

Comments

@ArgonAlex
Copy link

ArgonAlex commented Dec 10, 2019

Bug report

What is the current behavior?
I was actually trying to make a minimal reproduction for #8677 and ended up with this error. I'm not sure if it's related or not. It seems to happen with some specific combination of static and dynamic imports between multiple entrypoints.

If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?
I would expect __webpack_require__.e to be defined or not referenced. Disabling module concatenation causes it to be defined, but I don't know if that feature is the root cause of the issue.

Other relevant information:
webpack version: 4.41.2
Node.js version: 12
Operating System: OSX

sokra added a commit that referenced this issue Dec 17, 2019
sokra added a commit that referenced this issue Dec 17, 2019
sokra added a commit that referenced this issue Dec 17, 2019
@sokra sokra closed this as completed in c81963b Dec 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant