Mark Dalgleish

I put together an example of using Remix 3 with Storybook via its lower-level `html-vite` framework. I wasn't sure how to do this going in, so this was a fun exercise! github.com/markdalgleis...

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...

"Let's hear it for the UN of Javascript! Vite: The Documentary is finally here. If you missed the premiere, it's OK!!! Here's the link so you can watch it again, and again and again. youtu.be/bmWQqAKLgT4 "

RR + unstable RSC support has shipped. Please give it a go and let me know about any pain points. remix.run/blog/react-r...

This is very exciting! React router and Parcel has shown the proper boundary of RSC support between application layer and as bundler layer. Jacob shared their work with me early and that has been guiding me better for RSC support on Vite. Thanks for the shout out in the post!🙏

RSC support in React Router powered by Parcel! 🤩

Check it out - RSC in React Router! Been working on this with @ebey.bsky.social and @markdalgleish.com for a little bit - pumped for folks to start playing with it! remix.run/blog/rsc-pre...

React Router v7.5 brings a revolutionary approach to lazy loading route code. You can now lazy load individual route properties instead of everything at once, making your initial load time lightning fast! => remix.run/blog/faster-... by @markdalgleish.com

I wrote a blog post 👀👇 In React Router v7.5 we’ve introduced a faster, more granular way to lazy load routes. This new API was designed to support the upcoming middleware API, but it also unlocked some extra performance optimizations across the board. remix.run/blog/faster-...

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 💍

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-...

So excited for this @vite.dev documentary. I really enjoyed watching the @react.dev one.

🚀 Just published a blog post about the new Split Route Modules feature I shipped in React Router v7. remix.run/blog/split-r...

$ pnpm create react-router

You guys aren’t going to believe this, but today I used a cable from my big box of old cables.

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 😎

> someone says something funny on the group call > unmute > laugh > mute

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.

Having DeepSeek on my laptop gives me a similar feeling to seeing physical encyclopedias on the shelf at home when I was a kid.

We should all agree to start rebranding “plugins” to “mods.” So much cooler.

When competing framework authors hang out at a conference.

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.

Merry Christmas! 🎄

React Router v7 is now an option in create-vite when spinning up a @react.dev + @vite.dev app: github.com/vitejs/vite/... Thanks @alem.forge42.dev and @patak.dev 🙏

Every week I get more validation that moving Remix (now React Router) onto @vite.dev was a good idea. This week is no different! bsky.app/profile/rphl...

👀

👀

React Router v7 is here! With framework mode, everything that made Remix great is now built into React Router. remix.run/blog/react-r...

This is becoming a tradition where I always post when @johnresig.com follows me on any social media platform. Always makes my day. He was my original open source hero.

It makes me very happy to see so many people enjoying this talk 🙏

People aren’t going to remember me for CSS Modules. They’re gonna remember me because of this.

This post currently has more likes on Bluesky than Twitter. That’s super interesting.

Hey, I can see who liked other people’s posts again. I missed that.

Highly recommended talk. Mark is a fantastic story teller, and Remix adoption of @vite.dev and their rebrand to React Router is one of the most impactful tales of this year.

“How React Router Became a Framework,” my talk from React Advanced in London, is now up! Learn about why Remix as it exists today is being merged into React Router, and what it means for the future of the project. www.youtube.com/watch?v=BKi4...

Oof, I feel like I always get caught out that pnpm happily runs Node CLI scripts without the hashbang at the top but npm throws an error. If I haven’t set it up correctly: pnpm create … ✅ works npm create … ❌ fails

Like almost all social media platforms in their early days, the vibes are great right now because everyone’s posting about the things they love. It always goes south when everyone starts posting about the things they hate. How about this time we all agree to keep it this way?

Hello again 👋

Interesting. Notable drop in Twitter followers and a notable increase in Bluesky followers.

Positional args with primitive types make me nervous. e.g. function processCss(path: string) {…} Consumers might get confused and think they need to pass a string of CSS. Typescript won’t complain. That’s why I prefer this: function processCss(args: { path: string }) {…}

I’m kinda feeling like all the bell curve memes on tech choices are really just a proxy for this.

That feeling where you’re super passionate about a technical topic but you’re also painfully aware you might be in the middle of the bell curve meme.

I’m not gonna lie. When you lay out the current state of ES Modules and what it means for package authors, it kinda makes me wish we’d just stuck with CJS.

I have mixed feelings on Tailwind. - It’s an elegant solution to a bunch of different problems. - It’s an obvious choice due to its popularity. - From a design system perspective, I’d prefer consumers use components, not CSS. - Otherwise, I’d want class usage to be type safe.

Is JavaScript becoming PHP? I hope so. We could definitely learn a lot from them.