Skip to content

Pin nuxt-app to Node 22 to fix Vercel ERR_REQUIRE_ESM #174

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
denbec merged 1 commit into from
May 6, 2026
Merged

Pin nuxt-app to Node 22 to fix Vercel ERR_REQUIRE_ESM #174

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 nuxt-app/.nvmrc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1 @@
v20
v22
42 changes: 3 additions & 39 deletions nuxt-app/package-lock.json
View file
Open in desktop

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

3 changes: 3 additions & 0 deletions nuxt-app/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,9 @@
"name": "nuxt-app",
"version": "0.0.0",
"private": true,
"engines": {
"node": ">=22.12.0"

@chatgpt-codex-connector chatgpt-codex-connector Bot May 6, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Pin Vercel's engine range to Node 22

When this Vercel project deploys from nuxt-app, >=22.12.0 is an open-ended range that also matches Node 24, so it does not actually pin the runtime to Node 22. Vercel's Node-version docs say engines.node overrides project settings and their examples map broad ranges like >=20.0.0 to the latest 24.x version, while only 22.x/^22.0.0 map to latest 22.x; with 24.x currently available, this can deploy the SSR functions on Node 24 instead of the intended Node 22 and reintroduce untested runtime behavior despite the .nvmrc change.

Useful? React with 👍 / 👎.

},
"scripts": {
"build": "nuxt build",
"dev": "nuxt dev",
Expand Down