Main

React

🚀 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()`!

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.

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

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.

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 🤡

React (TanStack) Query is once again the absolute 🐐

Frontend

Valtio: fine-grained reactive state manager using JavaScript `Proxy` objects

https://valtio.dev

https://github.com/pmndrs/valtio

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.)

🔮 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

Ugh. Saw some really nasty React code.

*LOOKS AT WHO TH F WROTE THIS*

Damn, it was me.

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

React Native

We’re making the first moves to make the React Native Porto Meetup happen! 🇵🇹

If you live near OPO (or would like a reason to visit 😉) join below!

https://x.com/i/communities/1893250764107137175

React Native 🤝 Porto 🇵🇹

https://warpcast.com/thiagobrez/0x87cc07f1

Best of luck to anyone still maintaining a create-react-app in 2025 😅

https://react.dev/blog/2025/02/14/sunsetting-create-react-app

Facebook created create-react-app way back in 2016 to be the definitive “starter template” for production-ready React apps, using Webpack as the bundler, Babel for JavaScript transpilation, PostCSS for CSS transpilation, a bunch of local Node.js scripts to spin up a dev server and automate tasks, and (optionally) polyfills for porting Node.js-exclusive functionality to the browser. It was last updated in 2021 and is starting to show its age.

HTML/CSS/JavaScript bundlers have come a long way since Webpack – Rollup, Browserify, Parcel, ESBuild, Snowpack, Vite, Turbopack, Vinxi, Bun. Newer ones like Vite come with a CLI and a streamlined plugin ecosystem which replace what these disparate tools and scripts did before, making migrations, config files and tooling choices MUCH simpler for devs.

The legacy of CRA: memories of slow bootup times, package.json migrations gone awry, config files no one dared to touch, and a time capsule of the rich and chaotic history of the JavaScript tooling ecosystem. 🫡

create-react-app is finally getting deprecated.

End of an era. 🫡

https://x.com/housecor/status/1885047720102051858