Test the Node.js example - #657
Merged
Merged
Conversation
ledsun
marked this pull request as ready for review
August 15, 2026 13:53
kateinoigakukun
approved these changes
Aug 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I’d like to add more examples of
ruby.wasmfor Node.js. However, while there are currently end-to-end tests for the browser examples, there are no automated tests for the Node.js examples.I added a Vitest smoke test that runs existing Node.js samples as child processes.To ensure the samples remain unchanged, I created an isolated, temporary
node_moduleslayout.The sample test runs using only the
ruby-head-wasm-wasipackage.I also updated
CONTRIBUTING.mdto explain how version-specific packages invoke the shared test suite.