3 ms·

The change occurred in [March 2023](https://github.com/facebook/react/pull/26380 https://github.com/facebook/react/pull/26380) [^1^], and it became a hot topic

The change occurred in [March 2023](https://github.com/facebook/react/pull/26380 https://github.com/facebook/react/pull/26380) [^1^], and it became a hot topic 15 months later? [^2^] Are React release cycles that long? What's up with the title that it "almost" was slower if it was released? I assume I'm missing some context here. [^1^]: grep "This happens because of the following PR:" [^2^]: article publication date is June 17, 2024, tweet screenshots are dated between June 10th and that date

Uvix 2y ago
Yes, the release cycles between major versions are that long; v18 was released March 2022.
- refulgentis 2y ago
  Wow. 2y3m and counting (presumably, given article title). It's very straightforward, yet a complete surprise to me. I guess I'm just replying to invite someone else to give me a long-winded explanation of how the JS ecosystem works. ex. now I'm flummoxed as to how Vercel/next.js exists/releases new features, if they're based on React. Seems you'd either get stuck living on React top of tree, unreleased, or have an unholy merge to do.
  - Uvix 2y ago
    React in particular puts out a point release with breaking change warnings, along with an upgrade guide, several months before the next major version so that developers have plenty of time to prepare for any required changes. (For React 19, this was the 18.3 release at the end of April 2024.) They also try to provide scripted code updates ("codemods") to ease the upgrade process. This is admittedly rare in the JS ecosystem.
  - SahAssar 2y ago
    > now I'm flummoxed as to how Vercel/next.js exists/releases new features They run on canary react releases. It's a not that hidden dirty "secret".
norman784 2y ago
AFAIK React 19 was tagged as RC recently, so that could be the issue, people where not using React 19 in the frontend because of not being ready

Uvix 2y ago

Yes, the release cycles between major versions are that long; v18 was released March 2022.

refulgentis 2y ago
Wow. 2y3m and counting (presumably, given article title). It's very straightforward, yet a complete surprise to me. I guess I'm just replying to invite someone else to give me a long-winded explanation of how the JS ecosystem works. ex. now I'm flummoxed as to how Vercel/next.js exists/releases new features, if they're based on React. Seems you'd either get stuck living on React top of tree, unreleased, or have an unholy merge to do.
- Uvix 2y ago
  React in particular puts out a point release with breaking change warnings, along with an upgrade guide, several months before the next major version so that developers have plenty of time to prepare for any required changes. (For React 19, this was the 18.3 release at the end of April 2024.) They also try to provide scripted code updates ("codemods") to ease the upgrade process. This is admittedly rare in the JS ecosystem.
- SahAssar 2y ago
  > now I'm flummoxed as to how Vercel/next.js exists/releases new features They run on canary react releases. It's a not that hidden dirty "secret".

norman784 2y ago

AFAIK React 19 was tagged as RC recently, so that could be the issue, people where not using React 19 in the frontend because of not being ready