Skip to content

Fix MINIMAL_RUNTIME_STREAMING_WASM_INSTANTIATION under node. NFC #24782

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

Merged
merged 2 commits into from
Jul 24, 2025

Conversation

sbc100
Copy link
Collaborator

@sbc100 sbc100 commented Jul 24, 2025

We cannot actually use this API under node since the fetch API doesn't support local files.

However, this failure was going undetected for two reason:

  1. The test was only looking for the string 'hello' in the output which also appears in backtraces.
  2. The instantiation error was being swallowed by a catch block that simply printed the error the console, so the node process was exiting with success.

We cannot actually use this API under node since the fetch API doesn't
support local files.

However, this failure was going undetected for two reason:

1. The test was only looking for the string 'hello' in the output which
   also appears in backtraces.
2. The instantiation error was being swallowed by a catch block that
   simply printed the error the console, so the node process was exiting
   with success.
@sbc100 sbc100 requested review from dschuff and kripken July 24, 2025 00:24
Co-authored-by: Alon Zakai <alonzakai@gmail.com>
@sbc100 sbc100 merged commit 71ec929 into emscripten-core:main Jul 24, 2025
3 of 13 checks passed
@sbc100 sbc100 deleted the minimal_runtime_node branch July 24, 2025 17:33
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.

2 participants