Skip to content

Node.js 20 Support (18 reaches end-of-life on April 30, 2025) #10151

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 of 9 tasks
nbelyh opened this issue Mar 12, 2025 · 5 comments
Open
1 of 9 tasks

Node.js 20 Support (18 reaches end-of-life on April 30, 2025) #10151

nbelyh opened this issue Mar 12, 2025 · 5 comments
Assignees
Labels
area:spfx Category: SharePoint Framework (not extensions related) sharepoint-developer-support sharepoint-developer-support status:fixed-next-drop Issue planned to be fixed in an upcoming release. type:bug-confirmed Confirmed bug, not working as designed / expected.

Comments

@nbelyh
Copy link

nbelyh commented Mar 12, 2025

What type of issue is this?

Question

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

  • SPFx 1.20
  • Node.js 18

Issue description

Will the update to Node.js 20 be available before Node.js 18 reaches the end of life?

@nbelyh nbelyh changed the title Node.js 20 Support (Node.js 18 reaches end-of-life on April 30, 2025) Node.js 20 Support (18 reaches end-of-life on April 30, 2025) Mar 12, 2025
@Ashlesha-MSFT
Copy link

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

@Ashlesha-MSFT Ashlesha-MSFT self-assigned this Mar 12, 2025
@Ashlesha-MSFT Ashlesha-MSFT added the sharepoint-developer-support sharepoint-developer-support label Mar 12, 2025
@Ashlesha-MSFT
Copy link

@nbelyh,
Thank you for raising this question.
We will reach out to the engineering team for more clarity on the plans regarding the update to Node.js 20 in relation to SharePoint Framework support. We will follow up once we have more details.

@VesaJuvonen VesaJuvonen added status:fixed-next-drop Issue planned to be fixed in an upcoming release. type:bug-confirmed Confirmed bug, not working as designed / expected. and removed bug labels Mar 20, 2025
@jonathanhotono
Copy link

jonathanhotono commented Mar 24, 2025

@Ashlesha-MSFT Please consider upgrading typescript and react version as well..

@VesaJuvonen
Copy link
Contributor

Just to follow up on this. SPFx 1.21 beta 2 is now out with the Node.js 22 version support - see release note at https://learn.microsoft.com/en-us/sharepoint/dev/spfx/release-1.21

We will be skipping Node.js 20 completely and starting from 1.21 only version 22 is supported to align on the supportability of Node.js. ETA on the general availability of 1.21 is on the week of 21s of April.

We have shared in status and progress in the bi-weekly Thursday community call (yesterday's recording at https://www.youtube.com/watch?v=JxmmqVDrhGM). TypeScript 5 support might still be included in the 1.21. React update will be included in the 1.22 release later this year. SPFx and 3P support on React is unfortunately dependent on the React version which is used by 1P (out of the box web parts) so the update is dependent on the 1P updates.

@VesaJuvonen VesaJuvonen added the area:spfx Category: SharePoint Framework (not extensions related) label Apr 8, 2025
@nbelyh
Copy link
Author

nbelyh commented Apr 12, 2025

I have tested with the beta 2, works fine with me 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:spfx Category: SharePoint Framework (not extensions related) sharepoint-developer-support sharepoint-developer-support status:fixed-next-drop Issue planned to be fixed in an upcoming release. type:bug-confirmed Confirmed bug, not working as designed / expected.
Projects
None yet
Development

No branches or pull requests

4 participants