Remix Blog: Shop.app Case Study

[zealous relic]

https://remix.run/blog/shop-case-study

Feel free to retweet If you'd like to give us some love on twitter

Remix 💿 (@remix_run) on X

Did you know that https://t.co/RBMSWEMCzu is built with Remix? 😅

@Shopify is building and shipping products to millions of users with Remix. We sat down with the team who built https://t.co/RBMSWEMCzu to discuss the project.

https://t.co/RBMSWEMCzu was one of the first Remix…

Twitter · Mar 20, 2024, 4:19 PM

[woven scaffold]

Would be very interested in any technical details on "The team was able to reduce HMR times even further by parallelizing the build process for their style system, Tailwind CSS. Once parallelized, HMR times decreased all the way down to 0.1s.".

A lot of Remix users use tailwind so this could help many of us I'd imagine.

[zealous relic]

For sure, though with Tailwind v4 coming out and being a Vite plugin I don't think this will be a problem for long

[woven scaffold]

Thanks Brooks! That's true though unless it's super backwards compatible it could take us quite a while to migrate to v4, so it would be nice to understand the team's approach in the meantime.

[zealous relic]

I think they're just using something like concurrently and running the tailwind cli in watch mode

npx tailwindcss -i ./src/input.css -o ./src/output.css --watch

Ah, found it

"dev": "concurrently \"tsx ./server.ts\" \"tailwindcss --watch -o ./app/assets/css/tailwind.css\"",

[woven scaffold]

Awesome thanks so much Brooks, HMR is very fast already with Vite but will see if this makes it even faster.

[zealous relic]

Let me know if it makes a difference! I can definitely update the case study to include a little snippet and callout about v4

[woven scaffold]

Initial quick test shows it as a better approach as currently app.css is hot reloaded on every file change in our setup, the cli is better since it only reloads on new tailwind classes. However the cli isn't as well integrated so now CSS font imports aren't being bundled, so I probably need to mess with post-css plugins. Maybe v4 will be best of both worlds.