React 17

preview_player
Показать описание
React 17 is coming, so let's talk about all the new features that will be available!!

code used in video:

example of ref becoming null:

#benawad #react

----
Checkout my side projects:

----

----

----
Follow Me Online Here:


----
#benawad
Рекомендации по теме
Комментарии
Автор

it's somehow comforting to listen to Ben read changelogs even when I've already read them myself

ibiyemiabiodun
Автор

concurrent mode is stuck at a loading spinner...ah the suspense!

rtorcato
Автор

The real elephant in the room is that new blue lightning 😃
When will you be using the whiteboard behind you? 🤔

wcandillon
Автор

*Angular2 makes one large release*
Everyone: Boo Angular
That's why we need boring React releases

kinyakorirotti
Автор

You're the first geeky standup artist I've come across

Sashankyt
Автор

Another great and short video, full of useful info. Thank you for saving my time form reading all that.

abhishekpratap
Автор

Thanks for the TL;DR. Was nice to see you show examples to make more sense of the changes

benjidaniel
Автор

love the lil touch on the light ben. also your skin looks really good

ufufu
Автор

Keep up the good work. You're my number one resource for staying up to date on the latest web techs.

squashtomato
Автор

Boring is fine, I think it means we have found a stable release that everybody enjoys to write with. The new features (Suspense, Concurrent, etc) will just slot in and people can start using them but there's nothing inherently wrong with the current React I guess.

Also, hi ben 👁👄👁

mrelec
Автор

The ref issue is only a problem if you are using the ref to point to a react node (html element or react component instance). In this case ref.current is set to undefined when the component unmounts, and the effect cleanup now fires after that. Actual cases where this causes problems are removing event listeners and calling functions on child class components. If you are only using ref as a state that doesn't trigger a rerender you are definitely fine.

MultiMrAsd
Автор

React: updates
Preact: aw shit, here we go again

rishabhanand
Автор

12:25 Have you tried manually setting the `displayName` property for each component you render in order to improve the stack trace?

graystraytomcat
Автор

The code sandbox examples helped a lot. Much better than just reading patch notes.

metropolis
Автор

I wish i understood JS so this would mean something to me

orion
Автор

Yeah, there is a new language its called Oogaiuyavimi. React uses it to log errors to the users in production.

dimitarvel
Автор

love this review of updates, i am too lazy to read the documentation. Please keep it coming, thank you !

aqua
Автор

When you were testing the useEffect bug your "Problems" output seemed to have a few issues. Did you check them?

alichamas
Автор

React with this release v17 they more focusing in the future, they want easy to upgrade from v17 - +next released .
We don’t need major release every time, we need more secure & maintainable.

aseel
Автор

_"What's up Youtube, it's ya boi __-Dylan-__ Ben. I'm a reaction coach and today I'm gonna be reacting to reaction coach react-eses to react..."_

AstDerek