-
Notifications
You must be signed in to change notification settings - Fork 466
Our test infrastructure can't deal with async import() #1204
Copy link
Copy link
Closed
Labels
code maintenanceIssues that are not user facing, but are related the technical debt with the code itselfIssues that are not user facing, but are related the technical debt with the code itselfhelp wantedThings ready to be worked on by anyone. Issues must include instructions on how to complete the taskThings ready to be worked on by anyone. Issues must include instructions on how to complete the taskreadyIssue has defined requirements. It can be grabbed and worked onIssue has defined requirements. It can be grabbed and worked ontestsAnything related to testsAnything related to tests
Metadata
Metadata
Assignees
Labels
code maintenanceIssues that are not user facing, but are related the technical debt with the code itselfIssues that are not user facing, but are related the technical debt with the code itselfhelp wantedThings ready to be worked on by anyone. Issues must include instructions on how to complete the taskThings ready to be worked on by anyone. Issues must include instructions on how to complete the taskreadyIssue has defined requirements. It can be grabbed and worked onIssue has defined requirements. It can be grabbed and worked ontestsAnything related to testsAnything related to tests
In #1203 I'm trying to add a module that uses WebAssembly. WASM modules need to be instantiated asynchronously, so Webpack requires them to be in a code-split async chunk. So you need to use the
import()function to load such modules.However, our tests don't like the
import()call: they now fail with the message "Not supported":