Skip to content

Conversation

@ashi009
Copy link
Contributor

@ashi009 ashi009 commented Feb 10, 2025

node async wasm loader was incorrectly using output.environment.module
to determine if import.meta statement should be used. Which may not match
the output flavor defined by output.module.

What kind of change does this PR introduce?
bugfix

Did you add tests for your changes?
no

Does this PR introduce a breaking change?
no

What needs to be documented once your changes are merged?
no

Fixes #19209

node async wasm loader was incorrectly using output.environment.module
to determine if import statement should be used. Which may not match
the output flavor defined by output.module.
@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Feb 10, 2025

CLA Signed


The committers listed above are authorized under a signed CLA.

@alexander-akait alexander-akait merged commit a1edb20 into webpack:main Feb 10, 2025
63 checks passed
@ashi009 ashi009 deleted the cl/node-wasm-loader-module-aware branch February 10, 2025 23:57
@ashi009
Copy link
Contributor Author

ashi009 commented Feb 11, 2025

@alexander-akait may I ask when this will be released?

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

Successfully merging this pull request may close these issues.

node async wasm loader generates code using import.meta for commonjs

2 participants