fix(cli): forward node wasm flags #2041
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
--experimental-wasm-threads --wasm-atomics-on-non-shared-memory
These node options cannot be enabled via the
NODE_OPTIONS
environment variable, only via cli flags. But usingnode --experimental-wasm-threads --wasm-atomics-on-non-shared-memory vitest
only applies them tocli-wrapper
, not to any subsequently spawned processes. The proposed change adds them to the list of flags that Vitest forwards to spawned processes.