fix: filter npm warn stderr to unblock Node 24 deploys#203
Draft
kb-typeform wants to merge 1 commit intomainfrom
Draft
fix: filter npm warn stderr to unblock Node 24 deploys#203kb-typeform wants to merge 1 commit intomainfrom
kb-typeform wants to merge 1 commit intomainfrom
Conversation
Yarn 1.x re-injects npm_config_argv into child processes even after unsetting the env var. With npm 10+ (Node 24), this causes 'npm warn Unknown env config' messages on stderr. Jarvis treats any stderr output as a deployment failure, blocking the pipeline. The existing unset approach only clears vars in the parent shell but cannot prevent Yarn from re-injecting them. This commit adds process substitution to filter 'npm warn' lines from stderr while preserving real error output. Affects: frontend-deploy-workflow.yml, frontend-pr-workflow.yml
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
1 participant
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.
Yarn 1.x re-injects npm_config_argv into child processes even after unsetting the env var. With npm 10+ (Node 24), this causes 'npm warn Unknown env config' messages on stderr. Jarvis treats any stderr output as a deployment failure, blocking the pipeline.
The existing unset approach only clears vars in the parent shell but cannot prevent Yarn from re-injecting them. This commit adds process substitution to filter 'npm warn' lines from stderr while preserving real error output.
Affects: frontend-deploy-workflow.yml, frontend-pr-workflow.yml