Skip to content

fix(js): handle npm 11 warnings in stderr during registry version resolution #32223

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.

Sign up for GitHub

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
jaysoo merged 1 commit into from
Aug 5, 2025
Merged

fix(js): handle npm 11 warnings in stderr during registry version resolution #32223

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion packages/js/src/release/version-actions.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -111,7 +111,15 @@ export default class JsVersionActions extends VersionActions {
if (error) {
return reject(error);
}
if (stderr) {
// Only reject on stderr if it contains actual errors, not just npm warnings
// npm 11+ writes "npm warn" messages to stderr even on successful commands
if (
stderr &&
!stderr
.trim()
.split('\n')
.every((line) => line.startsWith('npm warn'))
) {
return reject(stderr);
}
return resolve(stdout.trim());
Expand Down
Loading
⚡