Fork me on GitHub
#react
<
2021-08-28
>
lilactown14:08:18

I should add a warning that says "this relies on internal implementation details of React and is subject to break on any version update. I've tested against React 17.0.2. Subsequent releases may correspond to different versions."

dominicm14:08:44

Presumably the same internals are used by react-dev-tools so they should be sufficiently stable?

lilactown14:08:22

that's right

lilactown14:08:36

I started this project on React 16.x and it hasn't changed much since then AFAICT

lilactown14:08:48

but of course react-dev-tools and React can coordinate their releases, since they're both developed by the same team. I on the other hand will only find out if things are broken if I try them out 😄

dominicm14:08:08

For react 16 I believe they had to issue a notice saying "oh and btw, we just broke react-dev-tools, here's the legacy version if you want it" or something to that effect?

lilactown14:08:15

i have a vague recollection of that but I also just read an article stating that react-dev-tools v4 supports back to React 13

lilactown14:08:30

but yeah if you're on < 13 you presumably have to use react-dev-tools v3

lilactown14:08:09

React 16 was the big architectural change to use fibers instead of the old vdom approach

lilactown16:08:02

looks like to make reagent concurrency safe we'll need to implement some sort of ref counting: https://twitter.com/lilactown_/status/1431623810638286851