chore(tools): suppress Node.js warnings in snap tests for stable output#1070
Merged
fengmk2 merged 5 commits intovoidzero-dev:mainfrom Mar 21, 2026
Merged
Conversation
✅ Deploy Preview for viteplus-preview canceled.
|
fengmk2
approved these changes
Mar 20, 2026
Member
|
|
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.
Add
NODE_NO_WARNINGS=1to the snap test environment to suppress Node.js runtime warnings (e.g.MODULE_TYPELESS_PACKAGE_JSON) that vary across Node.js versions.Why?
Without this, developers using a different Node.js version than the one pinned in
.node-version(22.18.0) will see warnings in stderr that get captured into snap output, causing false diffs unrelated to actual code changes.