Redux DevTools needs a local WebSocket server to talk to the app on the RN side. That means I have to support Node.js scripts in my plugin framework, which introduces major security risks. SES might help, but is it worth it? 🤔.

Redux DevTools are back in React Native DevTools! 🚀.Proves my custom panel injection method works - not just for small use cases, but for complex ones too.

Not every NPM package can be trusted - supply chain attacks are real. DevTools plugins are no exception. That’s why I’m sandboxing each plugin in its own execution context 🫡

One Callstacker suggested auto-discovery - scanning installed packages for DevTools plugins in package.json, so if React Navigation declares one, it activates automatically. I’m leaning towards explicitly listing plugins in Metro config for better security.

You won’t have to build the bundles yourself. CLI will handle that, make sure everything’s wired up right, and validate things like the manifest.

The vision for the RN DevTools plugin system is coming into focus. There’ll be two bundles: one for the Chrome UI, one for RN. I’ll define the comms protocol - your job is just to send messages through it. Might also need a manifest, similar to what Chrome extensions use.

There’s a way to inject custom panels into React Native DevTools without having to fork the entire frontend package. Let’s see where this takes me 🧑‍🍳

The worst thing that can happen during your sleep is waking up, realizing there are still a couple of hours left, closing your eyes again - only to hear your alarm ring and feel like you just blinked. I've been there today 🙃.

RT @mrousavy: (1/5) I'm super excited to announce 𝗿𝗲𝗮𝗰𝘁-𝗻𝗮𝘁𝗶𝘃𝗲-𝗻𝗶𝘁𝗿𝗼-𝗶𝗺𝗮𝗴𝗲 - an all new Image component for React Native, built entirely wi….

Is there a React Native debugging tool that supports plugins like Redux, TanStack Query, etc.? Think React Native DevTools, but easily extensible. Something you can build on for local insights without reinventing the wheel. Maybe I should build it? 🤔.

I'm going to strip the tool of all build automation and focus solely on Metro. With a solid foundation, supporting other flavors of RN apps will be much easier. With that in mind, you can expect an alpha release sometime next month.

I thought building a testing tool would be straightforward, but the deeper I get into it, the more problems I run into. There are so many ways to build your app - CLI vs. Expo, Metro vs. Re.Pack. Supporting them all is a tough nut to crack.

We're going live in just a couple of minutes - feel invited! 👀.

Vercel Ship is happening today and the React Universe is watching. I’ll be part of a livestream this Friday to break it all down - what’s new, what’s exciting, and what it means for React developers. If you’re up for a discussion about where the React is headed, join us.

When your testing tool can test itself… you know it’s growing up.

The beauty of testing on the React Native side? No fakery. Your Touchable is hidden behind an overlay? It won’t magically work - it’ll fail, as it should. Real UI, real results.

Just did a quick test run (URL support) in the cross-platform React Native test runner I’m building. ❌ Android: searchParams, pathname - totally broken.✅ Web: same code - all working. This is exactly why this tool needs to exist. Silent platform bugs are the worst.

RT @wesbos: ITS HAPPENING. Firefox 127 shipped today making it the first browser to support Temporal - the new API for working with Dates,….

Is it just me, or does Assassin's Creed Shadows look and run noticeably worse than Ghost of Tsushima on the PS5 Pro?.

Finally cracked it! Emulator auto-starts, app builds itself, Metro serves the test runner, and tests pass flawlessly. Next up: polishing the CLI to make it a world-class tool. Let’s go!🔥.