Skip to content

__webpack_require__.e is not a function #10104

@ArgonAlex

Description

@ArgonAlex

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions