🚨

0 reply

1 recast

20 reactions

Remote code execution vulnerability found in React Server Components v19. Upgrade ASAP and stay safe out there, folks. https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components https://x.com/reactjs/status/1996244264192274535

0 reply

0 recast

2 reactions

update your react dependencies a new hack has dropped today with vulnerabilities in several react server side rendering packages and next https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components

1 reply

1 recast

9 reactions

💀 https://x.com/davidkpiano/status/1990788603715465223

1 reply

0 recast

6 reactions

c'mon bro just one more hook bro

1 reply

0 recast

5 reactions

🚀 React Native 0.80 is here! Stabilized JS/TS API (opt-in strict types), no more deep imports, faster iOS builds (💨 +12%), and legacy arch is frozen. React 19.1 brings better error overlays with `captureOwnerStack()`!

0 reply

0 recast

0 reaction

Really says something about a language when so much effort goes into getting people to use abstractions on top of a fundamental primitive instead of the primitive itself. https://youtu.be/d3mhZbBOxbE

0 reply

1 recast

3 reactions

Five more hours of my life debugging a React-related issue that I'II never get back 🫠 You’re telling me if I want to conditionally render stuff that relies on state from a Provider, I have to break out the entire subtree into a `useMemo` expression to prevent the Provider from resetting its state whenever an unrelated component randomly decides to re-render?? Make it make sense 🤡

7 replies

2 recasts

11 reactions

It boggles my mind why anyone would willingly choose to write apps in this language in 2025. I don’t want to think about rendering cycles or where I’m calling functions from. I just want to write JavaScript.

4 replies

0 recast

6 reactions

😑

3 replies

0 recast

10 reactions

React (TanStack) Query is once again the absolute 🐐

4 replies

0 recast

5 reactions

Now this is a React state manager I can get behind. Just do property assignments and let the underlying JavaScript `Proxy` objects take care of the rest. No ugly `useState()` or `setVariableName()` functions in sight. (Notice how you can bypass the React Hooks runtime entirely by `subscribe()`-ing to changes.)

4 replies

0 recast

5 reactions

🔮 I tried Vibe coding with React Native. It's a double-edged sword: I liked it because I learned new things very fast (e.g. new iOS APIs I didn't know existed) I didn't like it because it's so easy to get your app in a broken and hard-to-recover state

4 replies

0 recast

15 reactions

Ugh. Saw some really nasty React code. *LOOKS AT WHO TH F WROTE THIS* Damn, it was me.

0 reply

0 recast

5 reactions

Biome users... how are you grappling with not being able to use the ESLint plugin for React Compiler.

1 reply

0 recast

1 reaction