Github workflow for nextjs: unhandledRejection ReferenceError: Headers is not defined

[zhiyuanouyang]

Hi,

I am new to Github Workflow and Nextjs. I simply created nextjs typescript project using npx create-next-app@latest (version is 14.0.0) and use the default nextjs workflow config generated by default in github.

Code is here.

The action log shows:

unhandledRejection ReferenceError: Headers is not defined
    at /home/runner/work/zhiyuanouyang.github.io/zhiyuanouyang.github.io/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:14:884[6](https://github.com/zhiyuanouyang/zhiyuanouyang.github.io/actions/runs/6679899847/job/18152433257#step:8:7)
    at /home/runner/work/zhiyuanouyang.github.io/zhiyuanouyang.github.io/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:14:41308
    at Object.<anonymous> (/home/runner/work/zhiyuanouyang.github.io/zhiyuanouyang.github.io/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:14:41329)
    at Module._compile (node:internal/modules/cjs/loader:1198:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1252:10)
    at Module.load (node:internal/modules/cjs/loader:10[7](https://github.com/zhiyuanouyang/zhiyuanouyang.github.io/actions/runs/6679899847/job/18152433257#step:8:8)6:32)
    at Function.Module._load (node:internal/modules/cjs/loader:911:12)
    at Module.require (node:internal/modules/cjs/loader:1100:19)
    at Module.mod.require (/home/runner/work/zhiyuanouyang.github.io/zhiyuanouyang.github.io/node_modules/next/dist/server/require-hook.js:64:2[8](https://github.com/zhiyuanouyang/zhiyuanouyang.github.io/actions/runs/6679899847/job/18152433257#step:8:9))
    at require (node:internal/modules/cjs/helpers:11[9](https://github.com/zhiyuanouyang/zhiyuanouyang.github.io/actions/runs/6679899847/job/18152433257#step:8:10):18)
Error: Process completed with exit code 1.```

I did not find out how to resolve this issue. I guess it seems sourced from nextjs package based on the logs? Does anyone ever see similar issues and know how to solve it?


<img width="1351" alt="Screenshot 2023-10-28 at 5 03 54 PM" src="https://github.com/community/community/assets/9460751/45017961-1428-43e1-80a2-3d9bfc7bb0af">

[OleksiiKachan]

if you look at the output of the step before build, you will see the potential issue - you install node 16, nextjs dropped the support of it in v14. if you want to use node 16, then use next 13, otherwise bump the node version

[mjdanbury]

For people (like me) who would benefit from a little more hand holding, this means that you have to go into package.json and add "engines": { "node": "18.17.0" }, then run

rm -rf node_modules

rm -f package-lock.json

npm install

and when that finishes, commit the changes and push to Github. That got things working for me.

[Lebraz98]

use nodejs 20 work correctly

[Likenttt]

It works like a charm. Thanks, Jawad

[Lebraz98]

Your Wlc

[clefersondannylo]

how do you changed the node version for to deploy ?

[OleksiiKachan]

https://github.com/actions/setup-node/blob/main/docs/advanced-usage.md#node-version-file

[idiglove]

Changing correct node version works! In my case, it was v18+

[nitinTJ]

I am using next 14.0.1 and node 20+, which is not working on the server where my production code reside.
But it works fine while generating build on my local machine.
I tried deleting node modules as well, but no luck.

[nitinTJ]

Removing dotenv module worked for me.

[Lebraz98]

remove .next and node_modules + use node v20.7.0 then run project

[faixanmalik]

what you mean by removing dotenv module worked
i have same issue but i cannot fix it

[autimio]

using the node version v20.10.0 worked for me

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬