remix VS turborepo

Also, Remix sourcemaps didn't work with Cloudflare Workers, but it seems that it should be working already. I should double-check it!

Then in this Github issue, I found something new and flashy, Paraglide JS.

Relates to https://github.com/remix-run/remix/pull/3104

The main goal of this project was to learn something new in a fun way, so I've decided to use Remix for it, and oh my - it was perfect. I was amazed by how powerful it is by using just standard web features such as cookies, query parameters, and forms. Just remember to be cautious when picking a starter template for your project. I picked the default one, and later found out it wasn't supported by Netlify. As a result, I had to delete the entire repository and start the configuration process again. 🙈

Real time data update: Remix supports Server Sent Events e.g. https://github.com/remix-run/examples/tree/main/_official-realtime-app https://github.com/remix-run/remix/discussions/2622

Sometimes the best way to learn is by looking at examples, so we’re going to walk through this Remix issue from Nick Taylor.

You don't need NextJS for SSR. There are less opinionated alternatives like Remix that was built by the React Router team and is backed by Shopify now, you can use something like Razzle or one of its alternatives for semi-opinionated pure SSR or follow the Vite Docs and just do it yourself with express.

- I've found Remix's configurable routes helps to split very large Remix projects into independent features that scales well, when multiple server output bundles drops this will scale the deployments across serverless functions also. RFC. PR.

Turborepo: Smart build system for JavaScript/TypeScript monorepos

We’ve only scratched the surface of what we can do with Turborepo. You can find more examples in the Turborepo examples directory on GitHub. Skill Recordings on GitHub is also another great resource that has been around since Turborepo was first released.

git clone https://github.com/vercel/turborepo.git

I use https://turborepo.org/ to facilitate my monorepo. Essentially it's a way of structuring your configs, UI; apps etc and you consume each like an internal package. I find benefits for this as the kinds of sites I make will generally have an internal app, an admin panel and a marketing site. I can write UI, config etc in one place and consume them over the three projects to keep everything consistent.

The latest addition to the Composer Suite monorepo, Turborepo optimizes monorepo workflows by caching build artifacts. This may sound a little abstract and boring, but what this actually means is that when you build something within your monorepo, Turborepo will make sure only the things that it depends on are rebuilt; everything else will be retrieved from a cache that either lives on your local computer, or a remote cache server. Adding Turborepo to the Composer Suite monorepo pretty much halved CI build times, but it was also a way to teach Vercel, which I use for hosting the various example apps in the repo, to only actually deploy the ones that have changed since their last deployment. And that's really cool!

NB: "Turbo" also has other meanings in a React Native context, so don't confuse Hotwire Turbo Native with Turbo Modules or Turborepo (as used in create-t3-turbo, mentioned later here).

Personally I just use this: https://github.com/vercel/turborepo/tree/main/examples/with-tailwind

To set up our monorepo we will use Turborepo which will take care of installing the basic parameters for us.