Theme updates and Node version support releases

[blackfalcon]

The Auro design system is currently undergoing updates to enhance theming capabilities across all web components, expected to release with BREAKING CHANGES around mid-summer.

Additionally, Node support is transitioning from versions 18 and 20 to versions 20 and 22, both classified as BREAKING CHANGES. Node v22, initially released on April 23, 2024, will enter its active LTS phase starting October 29, 2024, while Node v20 begins its maintenance mode on October 22, 2024.

Given this timeline, is it advisable to update Auro to support Node v22 by the end of July, considering the late October 2024 start for its LTS phase?

Updating Auro to support Node v22 by the end of July, even though the LTS doesn't start until late October 2024, can be considered from several perspectives:

Advantages:

1. Future-Proofing: Supporting Node v22 early means the system is ready for the latest features and improvements as they become stable and widely adopted.
2. Community and Ecosystem Alignment: Staying current with the latest Node versions can align with community practices and dependencies that might be moving to v22.
3. Testing and Stability: Early adoption allows more time to identify and address any issues before the LTS phase, ensuring a smoother transition when it becomes the default version.
4. User Preparedness: Users who prefer to stay on the cutting edge will benefit from immediate support, and this can demonstrate Auro's commitment to staying current.

Disadvantages:

1. Premature Adoption Risks: Since Node v22 will not be in LTS until October, it might still have some instability or bugs that could affect Auro's components.
2. User Base Impact: Users who prefer to wait for the LTS version might not be ready to upgrade, potentially causing friction or delays in adoption.
3. Additional Maintenance: Supporting a pre-LTS version might require more frequent updates and patches, increasing the maintenance burden.

Recommendation:

It is advisable to weigh these pros and cons and consider a phased approach:

1. Initial Support with Caution: Provide initial support for Node v22 with clear communication that it is not yet the recommended version until it reaches LTS. This way, users can choose to adopt it early if they wish.
2. Testing and Feedback: Use the time until October to gather feedback and perform thorough testing, ensuring that any issues are resolved before the LTS release.
3. Gradual Rollout: Encourage early adopters to use Node v22 and gather data on any potential issues. This information will be valuable for refining support before the official LTS period.

Given the timeline for the mid-summer release of the Auro design system update, aligning this major update with Node v20 as the primary supported version while providing optional support for Node v22 seems prudent. This approach ensures stability and readiness without forcing all users to adopt a pre-LTS version prematurely.

[blackfalcon]

We are closing this discussion as recent theme updates went out with breaking changes and the NODE version was NOT updated. Work will be addressed in a separate series fo discussions and tasks.