turborepo VS esbuild

GitHub: vercel/turborepo

When you setup a monorepo using turbo, the basic template gives you 3 packages by default. This can be found in turborepo/examples/basic.

Next, let’s create monorepo with Turborepo.

> Look at the dependency tree for a next

Looks ok to me: https://npmgraph.js.org/?q=next

Ironically, most of the dependencies are actually Rust crates used by swc and turbopack [1]. Try running cargo tree on either of those crates, it's enlightening to say the least. And of course, Node has a built in file watcher, and even the most popular third party package for file watching (Chokidar) has a single dependency [3].

[1] https://github.com/vercel/turborepo/blob/main/Cargo.toml

[2] https://github.com/swc-project/swc/blob/main/Cargo.toml

[3] https://npmgraph.js.org/?q=chokidar

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!

Use webpack or esbuild for bundling and pruning dead code Want to audit your bundle? Tools like pkg-size or cost-of-modules can show you which packages are inflating your deploy size.

I recommend using NodeJS, not because it fits the event-driven, non-blocking model, but because it is very well-suited for reducing file size by bundling the code. Esbuild is a great tool to bundle your Lambda. It is already included in the CDK construct NodeJSFunction when using AWS CDK, and you don't need source maps, at least not in production.

You will find an issue related to pureannotations in esbuild repository.

Vite (pronounced veet) was created by Evan You (Vue's creator) and launched in 2020. It uses native ES modules in the browser and esbuild for lightning-fast dev servers and Rollup for optimized production builds.

Pre-bundle all the dependencies on the "optimization boundary" list into node_modules/.vite/deps/ folder. This step is done by esbuild.

ESBuild is a bundler. The subtitle on the website is literally “An extremely fast bundler for the web”. To bundle, pass —-bundle flag.

https://esbuild.github.io/