Node.js 18 Support

[ghost]

Question 💬

Node.js 18 LTS is starting, but this repository restricts the use of Node.18 in the engine in package.json.
Bugs for Node.js 18 seem to be all closed, is there anything blocking support?

I opened a discussion before, but now that LTS has started, I'll post it here as well.
#5329

How to reproduce ☕️

---

Contributing 🙌🏽

Yes, I am willing to help answer this question in a PR

[ghost]

Reference: Node.js Release Schedule
https://github.com/nodejs/release#release-schedule

[panva]

v18.12.0 has not yet been released (as of 8:20 UTC) so technically this

now that LTS has started

is not true for the next couple hours and for all previously released v18.x versions.

[ThangHuuVu]

Let's keep this open to keep track of adding Node v18 to the engine compatibility list 👀

[ryanelian]

+1 to this and at the same time, allowing next-auth to be installed with the just-released Next.js 13

Right now next-auth cannot be installed with Next.js 13 using npm due to peerDependencies throwing errors.

[ghost]

Sorry for false start.
Thanks!

[daniharo]

next-auth won't work in Node 18 until openid-client dependency is updated to a new version which includes this commit: panva/node-openid-client@9aefba3.

Current version 5.1.6 gives this error:

openid-client@5.1.6: The engine "node" is incompatible with this module. Expected version "^12.19.0 || ^14.15.0 || ^16.13.0". Got "18.12.1"

Temporary solution is to use --ignore-engines when installing packages.

[nfts2me]

At least on Vercel using Node 18.x makes NetxAuth behave differently from 16.x branch.