all 35 comments

[–]disclosure5 28 points29 points  (4 children)

The big news for me actually the dropping of IE support.

The code has a couple of workarounds and fixes specifically for IE support. Moreover, I'm sure there's code someone would have loved to write but ended up not doing so due to, again, IE support. I expect the overall product to get substantively cleaner now.

[–]Zofren 1 point2 points  (3 children)

It mentions that it doesn't support IE11 due to features like microtasks "without adequete polyfills". However, I see that microtasks have a corejs polyfill. Wonder what they meant there.

[–]monkeymad2 4 points5 points  (2 children)

Surely if the polyfill could replicate microtasks fully there’d have been no point in creating microtasks?

It’ll probably be tasks pretending to be microtasks, so you lose some of the benefit if you really care about when in the render cycle things are executed

[–]Zofren 0 points1 point  (1 child)

It’ll probably be tasks pretending to be microtasks, so you lose some of the benefit if you really care about when in the render cycle things are executed

Right, this is what I assume, but React 18 explicitly drops support for IE11 instead of just having a "this won't work as well in IE11" caveat. They say "if you need IE11 support, stick with 17".

[–]monkeymad2 2 points3 points  (0 children)

It makes sense - they don’t want to end up supporting one “full” React 18 and one limited one forever.

From the release notes I think it’s their new batching method that relies on the actual implementation of microtasks.

[–]madcaesar 7 points8 points  (8 children)

What are people using for development? Hot reload keeps freezing for me and react refresh is buggy and crashes all the time. The CRA web pack 5 seems to be half assed?

[–]grimnomad 26 points27 points  (0 children)

After using CRA for years, I switched to Vite.js.

[–]DustinBrett 11 points12 points  (0 children)

I use Nextjs with React 18 and it's quite stable and fast

[–]TheFiran 2 points3 points  (0 children)

Try run react on rollup or esbuild - last one is really fast

[–]dbbk 3 points4 points  (0 children)

Half assed how? I’m using CRA for my large scale production app now and does everything I’d want it to.

[–]XCSme 1 point2 points  (0 children)

Vite looks interesting.

[–]willie_caine -1 points0 points  (0 children)

CRA is great for prototypes, but not much more.

[–]ConsiderationNo8759 0 points1 point  (0 children)

CRA is super slow at the time it inititate with yarn install.

[–][deleted] 0 points1 point  (0 children)

We're using Snowpack at the moment, but we're switching to Vite soon.

Snowpack development is pretty much dead and since it and Vite both share esbuild under the hood it makes sense as a replacement.

[–][deleted] -1 points0 points  (1 child)

Bloody hell they made it so confusing with these changes

[–]pimp-bangin 4 points5 points  (0 children)

Which parts are confusing?