Taskfile VS turborepo

https://github.com/adriancooney/Taskfile - my favourite for its simplicity. A shell alias and a shell script with a function for each "job". No need to learn yet another tool when you just want to run a few pre-defined commands from a project's root. I think, if you're going to complain about make, then maybe all you really need is a shell script.

You want to use $@ rather than $* so you don't have to do double-quoting on arguments that have spaces in them. That said, I'm gonna steal this. Also if you like clever composability tricks check out Taskfiles, I've adopted them all over in my own code.

I was amazed to discover Taskfile. Didn't realise it was a copy of Make.

https://github.com/adriancooney/Taskfile

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.