Azure / Azure/static-web-apps

[NodeJS][LTS] LTS version are never properly supported by the infra

Open
#1,534 16 comments 19 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
346
Forks
67
PR merge metrics
No merged PRs in 30d

Description

# Reminder: Goal is to have LTS available when it's active

EDIT: 13/02/2026
Image

Image

---
Is your feature request related to a problem? Please describe:
Docs page still mentioned Node 20 as "preview" while Node 22 is already LTS in 1 month:
![image](https://github.com/user-attachments/assets/335a0b60-fd86-477d-a8cf-90dabb08adb3)
![image](https://github.com/user-attachments/assets/610415aa-a6a5-4d01-9e0e-3eba5945e75e)

Describe the solution you'd like:
`node:20` should be / habe been the default since October 2023
`node:22` should already be supported in `preview`
that's why Node create STS version
and they also make `current` for future LTS, so that team owning a responsibility such as the azure backplane of maintaining the tooling should use that `CURRENT LTS` delay (or before) to start implemeting as preview the integration for the underlying customer

Describe alternatives you've considered:
There is none, the SWA backplane is owned by the Azure team + the Azure cli team

Additional context:
updating frontend application heavily depends on Node version on each major update of Next/Remix/.....

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.