Recently published a new version of the expo [react-navigation-visualizer](www.npmjs.com/package/@bam...) plugin, which shows your navigation state illustrated as a stack!
What's new:
- Navigation history
- Screenshot of the navigation states
- Navigation params display
Feedback is welcome!
Mercredi, @flexbox.bsky.social m'a invité pour parler avec lui de stack technique. 2 jours plus tard le podcast sortait déja !
We get late night German Doner Kebabs after conferences, even in Paris...
iykyk
after @reactnativeconnect.bsky.social
My video of @reactnativeconnect.bsky.social 2025 is so small that’s here the poster static version - static is always best anyway right? 😁 #hermes
Thank you @reactnativeconnect.bsky.social, I had an incredible time. The talks were amazing, I learned so much with each one of them!
Excited to share that I’ve teamed up with @antoinethib.bsky.social, @antoine-co.bsky.social, and @tychota.bsky.social on a new RFC to bring OkLab and P3 color support to #ReactNative! 🎨🚀 We’d love your feedback!
github.com/react-native...
How do you represent and debug your navigation state?
Here's my try: a react-navigation visualization tool based on expo dev-plugins
I would love to hear your feedback: would it be useful to you? What could I add?
It is available on npm, if you want to try it out! :)
www.npmjs.com/package/@bam...
When you say you don't use feature based code unless there is a good reason. What could be an acceptable reason for you?
I don't think I agree. Even if engineers rotate, isn't it simpler to approach a codebase with features, that you can visualize directly on the app/website? Even documentations are usually feature-oriented, at least from my experience
A screenshot of tldraw's experimental tldraw computer node-based ai interface. the nodes are set up to generate a random word, translate it to a target language, and then test the user on the word.
trying to implement a duolingo clone on @tldraw.com 😎 @steveruizok.bsky.social
Working on tap-to-highlight for my React Native (Expo) ebook reader app.
I do some very fiddly DOM traversal to dig into these <ruby> elements and send them off for tokenisation.
Sadly found that WebKit has many showstopper rendering bugs when using CSS Highlight API with <ruby>, though ☹️
