loading...

πŸš€ ReactJS v17.0 is out! πŸ”₯ No New Features

mrsaeeddev profile image Saeed Ahmad ・1 min read

Yeah!

ReactJS v17.0 is out with no new features.

The React team wrote on their official blog:

"The React 17 release is unusual because it doesn’t add any new developer-facing features. Instead, this release is primarily focused on making it easier to upgrade React itself.

We’re actively working on the new React features, but they’re not a part of this release. The React 17 release is a key part of our strategy to roll them out without leaving anyone behind.

In particular, React 17 is a β€œstepping stone” release that makes it safer to embed a tree managed by one version of React inside a tree managed by a different version of React."

βš›οΈ What do you think about the future of React?

Let me know in the comments!

πŸ‘‡ Link of the release blog post: https://reactjs.org/blog/2020/08/10/react-v17-rc.html

Discussion

markdown guide
 

Another important thing is the changed on the Event Delegation:

 

Can you elaborate or point me in the right direction?

 

Not the OP, but in general it means event listeners needed for delegations won’t be installed at document level anymore, but at app’s insertion point level, allowing multiple instances of React to run in the same document without the problems you’d face today. It’s a edge case, not something most of is should worry about.

Nicely explained, Valentin!

 

Thank you for pointing this out. It's a really important change.

 

A little bit disappointed there are no new features. But I understand the progression path. In order to ship some new cool features later a lot of applications need to prepare for it and need a smooth transition. Also allowing some legacy apps where migration would be too costly to have React 17 & the future React 18 side by side makes sense.

 

Yeah, same here. I am also expecting some cool stuff in v18.

 

This reminds me of a lot of the buildup for Drupal 9. After experiences sometimes bordering on traumatic for users upgrading from 6 to 7, or 7 to 8 (which ironically was less streamlined than migrating from 6 to 8 because they wanted to get people off 6 and finally make it EOL), they opted to make 9 "as simple as updating a point release in D8."

 

Yeah, exactly. I think now the ecosystem is set and everything is smooth. That's why they let it be that way.

 

There's still plenty in the works (e.g. concurrent mode, suspense for data fetching), and just look at how much has changed since v16 was released (completely new context API, hooks, etc.). But I think that they basically made it so those new features can essentially be "ready to go" in a future point release, just removing an experimental_ prefix if even that, without waiting for external API changes before the major version bump.

With that said, I'm definitely holding back on React Native for now, as it always rolls a little behind react-dom.

Yes exactly. There's plenty of work but I think after hooks they are pretty much clear about their direction.

 

☝ Just want to add that this is a release candidate.

 

Yeah, it is but still, people were expecting something from them.

 

Things are going smoothly as it supposed to be, personally I didn't expect any major changes or additional features. But R18 seems to be promising.

 

Yes, after hooks things are pretty much smooth I think. But v18.0 will be a major change I guess. Maybe they deprecate class components at all.

 

Sounds great!
but I was hoping for the characteristic suspense

 

Yeah, me too! But I think we will see it in the stable release.

 

I expected new features with v17.0. but their gradual upgrading approach will be better than new features.