Skip to content

chore(deps): update dependency @edge-runtime/jest-environment to v4 #826

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

Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update dependency @edge-runtime/jest-environment to v4 #826

Show file tree
Hide file tree
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
2 changes: 1 addition & 1 deletion packages/edge-config/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@
},
"devDependencies": {
"@changesets/cli": "2.30.0",
"@edge-runtime/jest-environment": "2.3.10",
"@edge-runtime/jest-environment": "4.0.0",
Copy link
Contributor

@vercel vercel bot Aug 19, 2025

Choose a reason for hiding this comment

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

The updated @edge-runtime/jest-environment@4.0.0 requires Node >=18, but this package specifies engines.node: ">=14.6", creating an incompatible dependency conflict.

View Details

Analysis

The package has been updated to use @edge-runtime/jest-environment@4.0.0 (line 48), which requires Node.js version >=18 according to its engine specification in pnpm-lock.yaml. However, this package declares it supports Node >=14.6 in its engines field (line 72). This creates a dependency resolution conflict where:

  1. Users with Node 14.6-17.x will be able to install the package (meets package engine requirement) but will fail when trying to install @edge-runtime/jest-environment@4.0.0 (doesn't meet dependency's engine requirement)
  2. Package managers may reject the installation entirely due to the conflicting engine requirements
  3. Tests using jest --env @edge-runtime/jest-environment (line 32) will fail on supported Node versions

This affects the test:common and test:edge scripts which explicitly use the @edge-runtime/jest-environment.

Recommendation

Either:

  1. Recommended: Update the package's Node engine requirement to "node": ">=18" to match the dependency's requirement, or
  2. Alternative: Downgrade @edge-runtime/jest-environment to a version that supports Node >=14.6 (likely staying on 2.x series)

If choosing option 1, verify that all features work correctly on Node 18+ and update any CI/deployment configurations accordingly.

"@edge-runtime/types": "4.0.0",
"@types/jest": "30.0.0",
"@types/node": "24.12.0",
Expand Down
115 changes: 5 additions & 110 deletions pnpm-lock.yaml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading