As Node.js 18 will end of life at April 2025,does Microsoft have migration plan?

[aStarProgrammer]

What type of issue is this?

other

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Target SharePoint environment

SharePoint Online

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

• browser version
• SPFx version
• Node.js version v18
• etc

Issue description

As Node.js 18 will end of life at April 2025,does Microsoft have migration plan?

[VesaJuvonen]

We are working on a plan here which will be communicated as soon as possible. SPFx is widely adopted worldwide with tens of millions of monthly active user on the 3P extensibility and we are committed on supporting this extensibility model also in future.

We will be sharing exact timeline and schedule as we get the plans confirmed.

[lafe]

@VesaJuvonen If you already have to update one critical component, it would be great to update the rest of the dependencies to the current versions. For example, React 19 has been released last year and SPFx still only supports React 17. TypeScript is a similar story and both outdated versions are already causing issues (for example, Tanstack Query 5 does not work with React 17). Fluent UI has also been updated to v9 and has major breaking changes, so starting new projects with Fluent UI 8 is ill advised...

Personally, I start to dread SPFx projects due to these issues. Our standalone SPA projects are much easier to maintain, and we have better control about every aspect of development, testing and the build process.

[andrewconnell]

Our standalone SPA projects are much easier to maintain, and we have better control about every aspect of development, testing and the build process.

So are Teams apps...

[OverkillTV]

Cutting edge technologies. Also meanwhile SPFx in SharePoint On-premises.....

[Ashlesha-MSFT]

Hello @aStarProgrammer,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

[Ashlesha-MSFT]

@aStarProgrammer, @andrewconnell,
As the conversation indicates that the migration is in progress, can we go ahead and close the issue?

[nikolaiessel]

@Ashlesha-MSFT Why do you want to close the issue? I not have seen any plan, only

We will be sharing exact timeline and schedule as we get the plans confirmed.

If somebody looks next month about the issue and it is closed, he would think "it seems th have been resolved" - but that´s not yet be done. Its kind of the same mentality of the bot´s that closes issues automatically if no comment is added in 2 weeks .oO

[andrewconnell]

100% agree with @nikolaiessel

Issues should be closed when they're no longer an issue, not closed based on a promise.

👉 As all developers know, not all promises resolve 😉

[Ashlesha-MSFT]

@andrewconnell, @nikolaiessel,
Thank you for your feedback. I understand your concerns regarding the closure of the issue.
We will ask the relevant questions to engineering team and provide you with an update as soon as possible. Your patience and understanding are appreciated.