Node 22 support

[elkay]

Description

Hey, I just tried to install this via NPM and it says it only supports up to Node 21. Are there any barriers to supporting Node 22? And if not, how soon will official support be added? Thanks!

Solution

Node 22 support added.

Alternatives

Not really any alternative to suggest.

Additional context

No response

[mrdoob]

Where does it say it only supports up to Node 21?

[elkay]

Oops, installing in this particular project with yarn, but I think that pulls from the same repos?

D:\AI-Content>yarn add three
yarn add v1.22.21
(node:30228) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
(Use node --trace-deprecation ... to show where the warning was created)
[1/4] Resolving packages...
[2/4] Fetching packages...
error @achrinza/node-ipc@9.2.8: The engine "node" is incompatible with this module. Expected version "8 || 9 || 10 || 11 || 12 || 13 || 14 || 15 || 16 || 17 || 18 || 19 || 20 || 21". Got "22.17.0"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

D:\AI-Content>yarn add three@latest
yarn add v1.22.21
[1/4] Resolving packages...
⠂ three@latest(node:29100) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
(Use node --trace-deprecation ... to show where the warning was created)
[2/4] Fetching packages...
error @achrinza/node-ipc@9.2.8: The engine "node" is incompatible with this module. Expected version "8 || 9 || 10 || 11 || 12 || 13 || 14 || 15 || 16 || 17 || 18 || 19 || 20 || 21". Got "22.17.0"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

[elkay]

Based on looking a bit more, looks like the problem is with a dependency of three, node-ipc:

https://github.com/achrinza/node-ipc

That package appears to be quite ancient based on the last update dates in the repo. There was a request by someone back in November 2024 to add Node 23 access and that was never responded to.

[elkay]

Oh hey.. actually, I looked in the package.json for that repo and it does appear they added Node 22 support.

https://github.com/achrinza/node-ipc/blob/main/package.json

"engines": {
"node": "14 || 16 || 17 || 18 || 19 || 20 || 22"
},

So maybe you just need to update to the latest of that package repo for now?

[elkay]

Disregard, closing. It's a nested dependency on my end for a package unrelated to three. Not sure why it decided to suddenly pop up now out of nowhere trying to add three specifically.

[elkay]

For anyone running into this issue that happens to stumble on this same error (mine was from using Vue), you can add the following to your package.json to get around it to upgrade and then get away from it.

"resolutions": {
"@achrinza/node-ipc": "10.1.11"
},