Node.JS needs to be updated

[robert4049]

The latest version of discord.js forces you to upgrade from version 16.

[AvarianKnight]

It doesn't make much sense to up the node version when the next LTS releases in two months

[tabarra]

Just to add that Discord.js as well as tRPC are not compatible with v16.9.x, and that Node.js v16 actually EOL'ed back in September due to security concerns regarding OpenSSL.

I'm eagerly looking forward to the brave and enthusiastic soul who can take on this important task, knowing that their effort will be much appreciated by many :)

[wowjeeez]

Hey, just to add to this discussion, Node.js V16 EOL'd a long time ago for multiple high severity CVEs, and many popular libraries are dropping support for the version, causing the V8 runtime to be incompatible with any of these packages.

I understand that there are a lot of moving things right now, but at the moment this bottleneck is holding back the ecosystem.

[mrclmtll]

Since now even Node 20.10.0 LTS is available wouldn't it be high time to update the node version of FiveM?
I mean you would have another 3 years of pause and we would be happy since the last commit to citizenfx/node was on December 20th 2021 (a29ea011b5a8073d866c57715ecd404051f907f4).

I mean the latest discord.js version which is working right now would be 12.5.3. In this version the replies are not even as you reply as a user but simply the @ of the user in front of the message.

[respectdevelopment]

Cfx. Update it :D.

[MehdiBenbahri]

I agree, the update should be done, at least to the last LTS.

[Jye-AU]

FiveM is running Node JS v16.9.1 which was released on the 10 Sep 2021. Node JS is now at v20.14.0 LTS . this makes it harder to create new resources for FiveM. are there any plans to update this?

Example trying to use nuxt JS

[thelindat]

are there any plans to update this?

Yeah but just like all the other plans cfx make it goes to the bottom of an ever-growing list that will never be resolved.

[MehdiBenbahri]

are there any plans to update this?

Yeah but just like all the other plans cfx make it goes to the bottom of an ever-growing list that will never be resolved.

A new hero just arise to save us from old nodeJS version :
#2479

[prikolium-cfx]

Let me update you with latest news.
Right now we have everything ready and testing NodeJS + client side V8 updates in-house.
I can't give you exact estimation on such update, but hope that we can deliver it to you in next 2 weeks, after proper testing.

[thelindat]

So are we finally getting the dozen of other v8 issues that people have been asking about (to no response) resolved or at least looked at?

[prikolium-cfx]

So are we finally getting the dozen of other v8 issues that people have been asking about (to no response) resolved or at least looked at?

Can you please send link to these issues?

[MehdiBenbahri]

Let me update you with latest news. Right now we have everything ready and testing NodeJS + client side V8 updates in-house. I can't give you exact estimation on such update, but hope that we can deliver it to you in next 2 weeks, after proper testing.

Thanks for the news !
That will open a huge possibility for us.

[thelindat]

• tweak(citizen-scripting-v8): increase heap size per isolate to match physical memory size seems this finally got attention
• UnhandledPromiseRejectionWarning: Error: BUFFER_SHORTAGE
• Async export returns incorrect value when second export is called after a value is awaited
• feat(citizen-scripting-v8): add ability to change max-old-space-size
• DRAFT: WIP/PoC: funcref correctness
• v8 exports type definitions conflict with @types/node

And I have brought this up ~6 times in releng.

fivem/data/shared/citizen/scripting/v8/main.js

Line 155 in 5e71f91

const rv = refFunctionsMap.get(ref).callback(...unpack(argsSerialized));

[VIRUXE]

Let me update you with latest news. Right now we have everything ready and testing NodeJS + client side V8 updates in-house. I can't give you exact estimation on such update, but hope that we can deliver it to you in next 2 weeks, after proper testing.

It's been three weeks. Could we get another update, please? Thank you.

[martonp96]

Let me update you with latest news. Right now we have everything ready and testing NodeJS + client side V8 updates in-house. I can't give you exact estimation on such update, but hope that we can deliver it to you in next 2 weeks, after proper testing.

It's been three weeks. Could we get another update, please? Thank you.

The updates are currently being tested by the community in the experiments section.

[DemmyDemon]

The updates are currently being tested by the community in the experiments section: https://forum.cfx.re/t/nodejs-20-and-v8-update/5246559

That page is private, so linking to it is meaningless. The vast majority of the community just get the forum "lol 404 go away" page.

[martonp96]

The updates are currently being tested by the community in the experiments section: https://forum.cfx.re/t/nodejs-20-and-v8-update/5246559

That page is private, so linking to it is meaningless. The vast majority of the community just get the forum "lol 404 go away" page.

Link removed, so here is some context.
The experiments section is new and currently only a few people have access. If someone wants to try the node updates regardless, they can try to request trough this link: https://forum.cfx.re/g/experiments
Keep in mind, that its only a status update about work on node, its not forgotten. Also requesting access will not guarantee that you wil get accepted.

[robert4049]

The updates are currently being tested by the community in the experiments section: https://forum.cfx.re/t/nodejs-20-and-v8-update/5246559

That page is private, so linking to it is meaningless. The vast majority of the community just get the forum "lol 404 go away" page.

Link removed, so here is some context. The experiments section is new and currently only a few people have access. If someone wants to try the node updates regardless, they can try to request trough this link: https://forum.cfx.re/g/experiments Keep in mind, that its only a status update about work on node, its not forgotten. Also requesting access will not guarantee that you wil get accepted.

Any further updates on this? I personally know of devs who have developed with the newer versions of node and have releases waiting on this update.

[jellyton255]

Any further updates on this? I personally know of devs who have developed with the newer versions of node and have releases waiting on this update.

The last word was that they were investigating an issue with performance and statebag writing and that it would be the last hurdle until it's pushed to canary, but that was a long time ago.

[FynniX]

Any update on this? Can't use current version of prisma as they need a higher version of node.

[DaniGP17]

Any update on this? Can't use current version of prisma as they need a higher version of node.

In the experimental section they have not said anything relevant about the current state, although I know that it is not the best, you can use an old version of prisma until they release this.

[tabarra]

Don't worry guys, I know things are still in motion, it will be released when it's ready to be released (hopefully soon 😋).
Just need to be patient a little more.

[riccardoconte7904]

Hi... any news? We're still on v16, even on the lastest 11xxx fxserver build...😅 Also, why is the latest recommended build a 7xxx? Are all the latter ones unstable?