turborepo VS esbuild

# .github/workflows/affected.yml env: # https://github.com/vercel/turborepo/issues/9320 TURBO_SCM_BASE: ${{ github.event_name == 'pull_request' && github.event.pull_request.base.sha || github.event.before }} steps: - run: npx turbo run format --affected - run: npx turbo run lint --affected - run: npx turbo run typecheck --affected - run: npx turbo run test --affected

Turborepo issue #3928: 21 upvotes asking for env var management

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

Vite uses esbuild written in Go, absurdly fast to pre-process your node_modules dependencies.

The Metadata section tells SAM how to build your TypeScript code. Instead of running tsc and bundling manually, SAM uses esbuild — a JavaScript/TypeScript bundler. It compiles your TypeScript, minifies the output, generates sourcemaps for debugging, and packages it all up. You don't need to install esbuild yourself — SAM handles it during sam build.

Good call out from that thread is he's trying to get a small change in esbuild added to help with this as well.

https://github.com/evanw/esbuild/issues/4419

The reality is simple: minification was never security. It's a size optimization that bundlers like esbuild, Webpack, and Rollup do by default. Variable renaming slows down human readers but LLMs read minified code like you read formatted code.

Very nice :)

For a while I've been annoyed that esbuild, which is written in Go, eschews these APIs to detect changes in watch mode and instead continually polls the filesystem: https://github.com/evanw/esbuild/issues/1527#issuecomment-90.... It actually consumes quite a bit of battery, so I might fork it and apply this post's implementation!

esbuild is written in Go and is 10-100x faster than JavaScript-based minifiers:

esbuild — fast JavaScript/TypeScript bundler

esbuild is still a Go app today: https://github.com/evanw/esbuild

The first hints of what become Bun were when Jared experimented at porting that to Zig.

In the following sections, we will explore how does it do what it does using one such tool called esbuild