Next.js, node.js 16 TypeError: Cannot set property Request of #<Object> which has only a getter

[NishantPacharne]

This is not a Bug Report, Feature Request, or related to Documentation

• I have searched the existing issues

Is there an existing issue for this?

• I have searched the existing issues

What's up?

Iam using next js and as soon as I put 'let Web3 = require('web3');'

I get these errors :-
TypeError: Cannot set property Request of # which has only a getter
This error happened while generating the page. Any console logs will be displayed in the terminal window.

Examples/References

No response

[nullvoidundefined]

I'm having the same issue. Just noticed it yesterday. I am also using Next.js. Se also: this Stack Overflow issue.

[NishantPacharne]

I'm having the same issue. Just noticed it yesterday. I am also using Next.js. Se also: this Stack Overflow issue.

Yeah for now I have also downgraded to version 1.7.4 .... then it is working

[kremalicious]

Same here. But let's be a bit more helpful in reporting what's wrong instead of just "I get these errors".

Exclusively happening when building with Next.js v13.0.2 on Node.js below v18. With Node.js v18 all is fine.

• web3.js v1.8.0 + Next.js v13.0.2 + Node.js v18 → all good!
• web3.js v1.8.0 + Next.js v13.0.2 + Node.js v16 → broken with reported error
• web3.js v1.7.4 + Next.js v13.0.2 + Node.js v16/v18 → all good!

Node.js v18 comes with native fetch support, and Next.js tries to polyfill things for below versions, and then fails on abortcontroller-polyfill, leading to reported error Cannot set property Request of #<Object> which has only a getter:

To reproduce:

1. New app with npx create-next-app@latest, go to created folder
2. nvm use 16
3. npm i web3
4. do import of module in .e.g pages/index.js: import web3 from 'web3'
5. npm run build
6. See error in console

[jdevcs]

@kremalicious Thanks for this info. Our team will be looking this issue,

[NishantPacharne]

Thanks Matthias! I'll update my node.js ..

[luu-alex]

Hey there, thanks for reaching out @NishantPacharne and thank you a ton @kremalicious for the detailed response. I have investigated this and created a PR to fix this issue. So next.js will start working properly with node v16, but for now for a quick fix, please switch and use node 18.

[bezlant]

Thank you so much. It took me 10 hours to figure out that it needed a different node version. I deploy on netlify so adding a .node-version file with the version needed (19.1.0 in my case) in the root folder fixed it.

[luu-alex]

Nodejs 16 build will work fine for next.js next release, thank you for all of this and will close this.