Skip to main content

πŸ“¨ #175: RSC, useSyncExternalStore, Vinxi, Server Actions, Next.js, Remix, margins, WakuLand, R3F-uikit, React-Forget, RN releases, Bridgeless, Expo Fingerprint, Flash Calendar, Zeego, RN Reusables...

Β· 9 min read
SΓ©bastien Lorber
Newsletter Editor - Docusaurus maintainer
Benedikt MΓΌller
Indie Hacker

Hi everyone!

This week has been rather quiet in terms of releases, but we have many great articles to read!

Sorry for last week, the email was so long that despite removing links, it got truncated by Gmail πŸ˜….

πŸ’‘ Check this newsletter on Twitter - visual format 🎨

To support me:

Don't miss the next email!

    πŸ’Έ Sponsor​

    CMS with Inline Visual editing for Next.js with App routing

    CMS with Inline Visual editing for Next.js with App routing

    Set up a project in just 1 minute with the CLI and define your own Visual blocks as React components to convey your pixel-perfect corporate brand, using any CSS framework. Try the new Next.js starter with Server Components!

    Content editors can easily use content blocks to compose pages visually, just like using a word processor, without compromising the design.

    React Bricks is enterprise-ready with Digital Assets Management, Advanced SEO, Real-time Collaboration, Scheduled Publishing, Multilanguage, integration with external APIs, Approval Workflow, Multiple environments, Change history and more.

    Trusted by corporate clients such as The Weather Channel, Deel.com, La Banque Postale, leading eCommerce sites and over 9,000 users worldwide.
    Get started today!

    βš›οΈ React​

    Instant Search Params with React Server Components

    Instant Search Params with React Server Components

    An awesome interactive article showing that it’s surprisingly hard to persist UI state to the query string in a React Server Component world and yet give immediate user feedback. Updating the URL triggers a server round-trip. The new useOptimistic hook solves this problem nicely. This also shows a nice use-case for CSS :has(), to avoid hoisting the startTransition pending state.

    Building a React Metaframework with Vinxi

    Building a React Metaframework with Vinxi

    TIL about Vinxi, a toolbox built on top of Vite and Nitro enabling you to easily create your own meta-framework, with support, SSR, routing conventions, server functions and everything. Solid Start uses it behind the hood, but it’s a framework-agnostic SDK. Apparently, TanStack Start will use it too! This article explains how to use it with React.

    Don't miss the next email!

      πŸ’Έ Sponsor​

      The most comprehensive User Management Platform

      The most comprehensive User Management Platform

      Clerk streamlines React app authentication and user management, ensuring a quick setup for the modern web.

      Experience the benefits of Clerk:

      • πŸ’… Pre-built UI components for sign-in, sign-up, user profiles, and organizations. Customize with any CSS library and deploy on your domain
      • πŸ“¦ SDKs for React, React Native, Next.js, Redwood, Remix, and other frameworks
      • ⚑ Integrations with Firebase, Supabase, Convex, and other BaaS providers
      • 🎁 User management, social login, magic links, MFA, and more out of the box

      Dive into Clerk's quickstarts and tutorials to kickstart your projectπŸš€

      πŸ“± React-Native​

      This section is now co-authored with Benedikt. Feel free to send us your comments by email or on Twitter!

      This past week, we all enjoyed a brief respite from major headline React Native news (or did I miss something, in this case @me). Perhaps that's a welcome change, especially after the whirlwind of events like Expo 50, visionOS, the State of React Native, react-strict-dom, and more. However, this doesn't mean the React Native world has come to a halt. There’s been a lot of little announcements that give us a glimpse in the near future of React Native. The first release candidates for RN 0.74 were released. They contain a lot of improvements as well as some deprecations and breaking changes, but from the first glance nothing major that makes me worried about upgrading effort. Most notably, bridgeless mode becomes the new default with 0.74 (but only when New Arch is enabled). Bridgeless mode is the third pillar of the New Arch, after the already introduced TurboModules and new renderer (Fabric). Speaking of New Arch and defaults, a PR was merged that’ll make the New Arch the default beginning with RN 0.75 (it will still be possible to opt out though). Also, the RFC with the React Native Frameworks definition has been merged, laying out the responsibilities of RN vs frameworks on top of RN.

      πŸ”€ Other​

      🀭 Fun​

      alt

      See ya! πŸ‘‹


      Don't miss the next email!