Pinned Tweet
We (@expo) are now maintaining React Native for Web. Thanks to @necolas for building it and looking after it all these years 🫡
github.com/necolas/react-nat…
Mathieu A. retweeted
Content mappers in TS 7.1 are an absolute game changer
It’s plugins for TypeScript: a way to dynamically compute a static type signature for external file types (.vue, .md, etc) and integrate them directly into tsc compilation
TypeScript 7.1 Beta is now available! Now with a preview API, content mapper support, new features, and some great optimizations. Give it a try and give us some feedback! devblogs.microsoft.com/types…
Mathieu A. retweeted
Je ne pensais pas de mon vivant voir une dictature se dessiner en France et encore moins sous les hourras d’une foule manipulée à qui l’on fait croire que le danger c’est un parti qui veut davantage d’égalité. Et pourtant les digues sautent.
I will be there 👋
Our first official React Foundation Meetup is here!
📅 Nov 11 · 6–9:30 PM GMT
📍 Meta Kings Cross, London
Great people, good conversations, and a Community worth showing up for.
You’ll want to be there 👇
luma.com/g9q690i2
Mathieu A. retweeted
Safe area insets just landed in RN core! The `experimental_onSafeAreaInsetsChange` on <View /> allows receiving inset changes in a synchronous callback. This means state changes that happens in it will render on the UI thread. Compared with react-native-safe-area-context:
react-native-edge-to-edge is now deprecated 🫡
All supported React Native versions (0.86+) ship many edge-to-edge fixes. Set edgeToEdgeEnabled=true in android/gradle.properties instead.
Thanks to everyone who used it, and to @expo for the support!
npmjs.com/package/react-nati…
Mathieu A. retweeted
Préfectures attaquées, commerces pillés, mairies saccagées ou brûlées, policiers blessés. Ce soir et demain, on va (à raison) beaucoup parler de casseurs. On parlera peut-être moins de ce qui nous a menés là : vingt ans d'impéritie au sommet de l'État.
Mathieu A. retweeted
Il faut absolument lire et partager cet article du @derspiegel
"La France a un gros problème de violence systémique. (...) Les notions de désescalade et de proportionnalité de la riposte ne font pas partie du vocabulaire de la police française" ⤵️

ALT Vu d’Allemagne. La France a un problème de violence, et il commence par sa police Alors que les manifestations de ce samedi 17 octobre vont être scrutées avec attention, la question des violences policières ressurgit. La brutalité avec laquelle les forces de l’ordre gèrent les conflits témoigne d’une vision archaïque de l’État, argue ce magazine allemand. Le citoyen est vu comme un potentiel ennemi, l’État comme le détenteur de la raison. Une conception responsable de bien des maux du pays.
SDK 58 is out 🙌
This SDK is built for iOS 27. Apps on SDK 58 will be ready for Duo on day one 📖.
The release also includes App Intents for Siri, 2x faster clean Android builds, faster Expo modules, and a CLI built for your coding agent.
Changelog: expo.dev/changelog/sdk-58
Upgrade: 𝚗𝚙𝚡 𝚎𝚡𝚙𝚘 𝚒𝚗𝚜𝚝𝚊𝚕𝚕 𝚎𝚡𝚙𝚘@^𝟻𝟾.0.0 --𝚏𝚒𝚡
Mathieu A. retweeted
React Native 0.88 is now available!
This release switches to a web-based event dispatching model, adds variable fonts support, SceneDelegate on iOS, and ArrayBuffer support for Android TurboModules. And it's another non-breaking major release.
reactnative.dev/blog/2026/10…
Mathieu A. retweeted
In the next version of Bun:
your software, hyper-optimized by a corporation with unlimited tokens, shipped as Bun™️
Mathieu A. retweeted
1/3 🧵 react-native-nano-icons 1.0 is out 🔬💎 and it brings some massive DX sugar.
Font icon rendering is insanely fast ⚡️ and so is generating it from your SVGs. Drop a Figma export into the repo and see it on screen in under a second with the new Metro plugin. No native rebuild.
You can also forge the same SVGs into native symbols for Liquid Glass bottom tabs on iOS and Material ones on Android 🧭
Examples and all features: nano-icons.swmansion.com
Follow the thread below to learn more 👇
2/3 🧭 Native tab bars can't render a React component like .
Nano Icons 1.0 forges native tab bar icons from the same SVGs: SF Symbol .symbolsets in the iOS asset catalog and VectorDrawables on Android. Liquid Glass and Material tabs from one SVG folder 💎
available with react-native-screens 4.29+ and @reactnavigation later today 🤓
Mathieu A. retweeted
Oh my god, Firebase’s SDK started to crash ALL iOS apps that were using it, for ALL sessions, just like that, no way for any of these apps to do anything…
How amateur is all of this from any SDK, but especially one from a company with as high of an engineering bar like Google…
github.com/firebase/firebase…
incase anyone has been wondering why their iOS apps are intermittently crashing since today morning 🙃
reminds me of the Facebook swizzling crash incident.
@Firebase pls help
STOP calling basic network misconfigurations as "emergent misalignment"
YOUR agent escaping YOUR sandbox via DNS egress is an infrastructure failure that YOU are directly responsible for, not the agent
That's so cool, thanks @DelphineBugner 🙏
Replying to @ReactNativeConn
@ReactNativeConn 2026 is a wrap! This year’s theme was Monet and Impressionism so obviously the drawings came back; this time with a focus on the speakers, who truly did an amazing work for all of their talks 💙 cheers to @FilipKaminski @ziusko @zoontek & @uffoltzl !
Mathieu A. retweeted
📦 Node 26.10 - Native support for throttle/debounce
I didn't expect this 😄
RIP lodash
TC39 proposal when?
Seems like I can't use my OSS Codex offer (ping @charliermarsh - what happens here? I'm on the free plan)
What surprises (and saddens) me the most about the new reality of agentic software engineering is how a majority of issue and PR descriptions are fully AI-written.
I would expect that most devs switch over to using AI to code (I use it too!), but then file the issue/PR themselves with a "Hi, this is what I tried to do, this didn't work, this is the fix". But no, about 90% of the issues I get on Mediabunny these days are fully AI written.
This is the new reality so I'll get used to it, but I personally find it hard to understand why it is like this. I know for myself that I would write the descriptions by hand because I want to communicate with the maintainers on a more personal level and let them know that I appreciate their work. Before agents, most of the issues I got looked like that.
Without this, OSS development feels much more lonely: you make software for other people and you mostly hear back from machines.
































