Skip to content

Build: Let wet-boew dependency use npm >=10.7.0#2729

Merged
Garneauma merged 1 commit intowet-boew:masterfrom
EricDunsworth:build-wet-boew-npm-10.7.0-greater
Feb 4, 2026
Merged

Build: Let wet-boew dependency use npm >=10.7.0#2729
Garneauma merged 1 commit intowet-boew:masterfrom
EricDunsworth:build-wet-boew-npm-10.7.0-greater

Conversation

@EricDunsworth
Copy link
Member

wet-boew/wet-boew#9924 previously changed it from ^10.7.0 to >=10.7.0, but GCWeb's package-lock.json file wasn't updated to match (was still set to ^10.7.0).

In practice, this change prevents "EBADENGINE Unsupported engine" warnings when running npm install in GCWeb via npm 11 (like in node.js 24.x)... and possibly beyond.

CC @nschonni @Garneauma

wet-boew/wet-boew#9924 previously changed it from ^10.7.0 to >=10.7.0, but GCWeb's package-lock.json file wasn't updated to match (was still set to ^10.7.0).

In practice, this change prevents "EBADENGINE Unsupported engine" warnings when running npm install in GCWeb via npm 11 (like in node.js 24.x)... and possibly beyond.
@Garneauma
Copy link
Collaborator

@BeraJosh For your review.

Copy link

@BeraJosh BeraJosh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No CVE/issues in the npm 10.7.0 module.
Approved

@Garneauma Garneauma merged commit 734e3f6 into wet-boew:master Feb 4, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants