Mark Dalgleish

@markdalgleish.com

🦄 CSS Modules co-creator / 💿 Remix + React Router at Shopify / 🧁 Vanilla Extract / MelbJS organiser / dad x4

I just created the “Remix 3 Resources” repo, collecting useful links related to Remix 3. It has *super* granular links to the Remix Jam live stream for each API, feature and demo, plus a bunch of demo apps and 3rd party integration examples. github.com/markdalgleis...

GitHub - markdalgleish/remix3-resources: A collection of useful links relating to Remix 3

A collection of useful links relating to Remix 3. Contribute to markdalgleish/remix3-resources development by creating an account on GitHub.

github.com

Same! I started using this before there were docs or any official announcement for it and was slightly concerned I was doing something I wasn’t supposed to 😅😅😅 Glad it’s now been made official 💍

Mark Dalgleish@markdalgleish.com · last yr.

Super excited to see @cloudflare.social launching v1 of their @vite.dev plugin, with first class React Router v7 support. Huge shout out to James Opstad for working with us to ensure support on top of our recent Vite Environment API work. blog.cloudflare.com/introducing-...

COMING SOON: Experimental @vite.dev Environment API support in React Router v7. Check this out — a single `vite build` command can co-ordinate a full client + multi-server build. Previously this was only possible via the `react-router` CLI. We're “just a Vite plugin” again 😎

Bild

With React Router’s upcoming Split Route Modules feature that I’ve been working on, I’ve got the chunk name in the build output now so it’s easier to tell what’s downloading when. Here’s a before and after in the network tab.

BildBild

Check out what I've been working on in React Router: Split Route Modules. Ryan put together a neat demo of why this is so great for perf. With your client loader split into its own chunk, it can start running ASAP, even before the route component finishes downloading. x.com/ryanflorence...

One thing I’ve changed my mind on when it comes to documentation is whether to discuss implementation details. The purist in me wanted to leave them out because “the whole point is you don’t need to know!” But in hindsight this paternalises consumers. It leaves them without a good mental model.