Long time front-end developer, enthusiastic climber, father of two, husband of one.
Enjoy using React, Node, and Module Federation to create ambitious UX.
@ReactNorway Seems to be an app specific for GitHub.
It’s built on top of React Doctor, which is the tool that actually checks the code and generates a score etc.
@BrooksLybrand@ReactNorway@reactjs@remix_run What og post do you mean?
The linked post in the original message here seems quite new, and also does not contain any indication that Remix 3 has anything to do with React.
@ReactNorway@reactjs@remix_run I think this is a bit misleading.
Remix and React Router are in fact completely separate now, to the point that Remix V3 isn’t even using React anymore.
Remix was merged into React Router a few years ago, and Remix V3 is a clean break from React and a fresh start for Remix.
@ryanflorence@alexdanilowicz This pattern is mainly used instead of setting state in useEffect, so an update will happen anyway. This way it will be 1 update instead of 2.
@ddunderfelt@steipete I’ve done this a lot lately, never had that issue. Sorry to say but you’re probably doing something wrong 😬
Maybe forgetting to also do the setPrevValue call inside the if?
@kurtextrem@rickyfm@tsAngelNunnez@infinterenders Fwiw, I've seen developers doing that to circumvent the set-state-in-effect eslint warning, which is probably not what we want. I've seen them using setTimeout and Promise.resolve do get around it.
Maybe something that could be fixed in the eslint warning.
@brophdawg11 Ok 🙂
I saw a prominent FE teacher mention it was an about to drop, so a bit surprised it wasn’t on your list. Fingers crossed for 2026 then.
@dev_TEMITAYO With Zustand you would probably combine with TanStack Query etc.
With RTK you also get the built in RTK Query and listener middleware etc. Modern redux is great.
Not used Zustand but probably great as well.
Happy with RTK for now.
@rickyfm@RyanCarniato Not sure it’s lost. It’s just not ready yet.
Said it before: The big issue with RSCs was releasing it without wide enough bundler support.
@tannerlinsley@jherr@reactjs@tan_stack It has previously come across a bit like “we know what we’re doing, so we won’t worry too much about those rules”. At least that’s how I’ve read it. Made sense to me since you do certainly know what you’re doing 😄
Anyway, was just curious which parts of TanStack this applied to.