I thought double invocation of useEffect in dev is to show suspense edge cases. I want to replicate a real double invocation, but when a component suspends, the useEffect isn't run. Is there a way to create a real world example for this or have I missed something?
Ah perhaps I figured it out, I need to render without suspending first, then suspend, then re render. So I think "Will fire twice in StrictMode" in @TkDodo 's article becomes a real issue, and the ref fix doesn't work in production either
I spoke about Design System APIs in React at the @remix_london meetup last night, my first public presentation in 6 years, and with the other speakers being @kentcdodds and @sidchatterjee there was a bit of pressure... Thanks to @_edmundhung and @catchpowle for organising!
I'm looking for a new UI or full stack developer contract.
- 20+ years web development experience.
- 9 years with React.
- Comfortable with Remix, Next.js, TypeScript, node, React Native.
I'll be free for a new contract from 17th June. Things I like: React, @radix_ui (primitives, themes, icons + colors), @remix_run, TypeScript, accessibility, design and UX. I'm excited to demo what I've been working on for the last few months very soon.
Announcing Radix Themes 3.0 and a custom color palette generator 🎉
In this release:
• New layout engine
• 11 new components
• Zero config setup with Astro and Remix
• New docs with guidance on layout and styling
Anyone managed to get @remix_run memory sessions or similar working with @vite_js during development? Every time vite reloads dependencies, the sessions clear