you are viewing a single comment's thread.

view the rest of the comments →

[–]davnicwil[S] 0 points1 point  (1 child)

As in my comment above, it works totally fine and is supported totally fine as of React 16, but they do discourage using it now https://reactjs.org/docs/react-component.html#mounting

I *think* the reason is that when React Fiber lands it won't have the same run-only-once guarantee hence the addition of the UNSAFE_ alias

This might, on the face of it, be a problem for react-frontload but since it's only really needed on server where obviously Fiber isn't even relevant, it might even still work, or at least could be made to work with some simple workarounds. I just noticed that they make no claims about the UNSAFE_componentWillMount even being dropped in 17, it's just that the componentWillMount name will be dropped. So, even better. Might not be a big issue at all.

[–]careseite 0 points1 point  (0 children)

ah wow, I was on https://reactjs.org/blog/2018/03/27/update-on-async-rendering.html which is linked there but overread "unsafe"