4 ms·
I'm working with some fairly large monorepos and compile times. To be completely honest, JS is the least of our concerns when it comes to build time, things are
by bastardoperator 5y ago
I'm working with some fairly large monorepos and compile times. To be completely honest, JS is the least of our concerns when it comes to build time, things are pretty snappy when compared to other code bases like C, and Java even with tools like Bazel.
- leerob 5y agoWhile we're initially focused on JavaScript and TypeScript codebases, you can already use Turborepo with any language as long as you define tasks through `package.json` scripts and use npm/pnpm/yarn workspaces. Turborepo is written in Go and uses `turbo` to build `turbo` in its own monorepo[1]. We're discussing more native support for other languages. It would likely be a commitment to a small subset of popular languages (e.g. Rust, Go, C++, Python) while still maintaining our goal of nearly zero configuration. [1]: https://github.com/vercel/turborepo/blob/main/turbo.json https://github.com/vercel/turborepo/blob/main/turbo.json
- rattray 5y agoThis was my hunch, but it'd be awesome to make that a little more clear on the homepage! Especially if you can link to an FAQ with more detail on the tradeoffs. When considering adopting a tool like this vs something more general-purpose like Bazel, I'd like to have a rough idea of how screwed I'll be when some non-JS/TS code gets added in the future.
- wdb 5y agoPlease consider .net / msbuild support too :)