---
title: Turborepo 1.11
description: Turborepo 1.11 sets the Rust-based foundation for the future of Turborepo.
date: '2023/12/05'
tag: 'web development'
---

<h1 className="text-center">Turborepo 1.11</h1>

import { Authors } from '#components/authors';
import { ThemeAwareImage } from '#components/theme-aware-image';
import { Date } from '#components/blog/date';

<Date>Tuesday, December 5th, 2023</Date>

<Authors
  authors={['gregsoltis', 'chrisolszewski', 'nicholasyang', 'alexanderlyon']}
/>

Turborepo 1.11 completes our migration to Rust and ships several developer experience improvements:

- [**Our new Rust-based foundation**](#unlocking-the-future-of-turbo-with-rust): We've finished the port from Go to lay the groundwork for better performance, improved stability, and new features.
- [**Group logs for improved readability**](#group-logs-for-improved-readability): You can now specify `--log-order=grouped` to organize your logs into distinct sections separated by tasks.
- [**Updated examples**](#updated-examples): Start with an example for Next.js, Svelte, Remix, Nuxt, and more.

Update today by running `npx @turbo/codemod migrate`.

## Unlocking the future of `turbo` with Rust

As we wrote about in [our blog post about the migration](https://vercel.com/blog/turborepo-migration-go-rust), we're excited to start seeing the benefits of our porting effort for Turborepo users. Rust has allowed us to surface more complexity in _our_ code so we're able to create a better experience in _your_ codebase in several ways:

- We've noticed a slight performance improvement right away for some use cases, even without doing much performance tuning in our code yet. We look forward to diving deeper into making `turbo` **even faster soon**.
- We were able to move incidental behaviors of globbing, paths, and encoding support to tested and supported behavior, giving us better confidence that we're handling your configuration as expected. Going forward, we'll be able to build features like validation and automatic bug-fixing codemods into Turborepo for **better stability**.
- We've quickly iterated on **enhancing error messages** in your monorepo as a feature for next release, giving you critical information for find the source of misconfigurations.
- We've been able to catch possible platform-related bugs much sooner, as Rust forces us to think about the differences between platforms and environments much more closely than Go. This **deepened reliability** removes an entire category of possible bugs from your repository.

If you find any problems that you believe are related to the new Rust codepath, you can opt back to the Go codepath using the `--go-fallback` flag and [report an issue on GitHub](https://github.com/vercel/turbo/issues/new?assignees=&labels=kind%3A+bug%2Cowned-by%3A+turborepo%2Cneeds%3A+triage&projects=&template=0-turborepo-bug-report.yml&title=%5Bturborepo%5D+).

## Group logs for improved readability

To make it easier to review your task logs, we've introduced the `--log-order` flag to output all logs from a task **after it finishes** rather than _as it writes_. This results in logs that are separated per-task, improving readability on a specific task's logs.

<ThemeAwareImage
  className="my-4 flex justify-center"
  light={{
    alt: 'Using `--log-order=grouped` to output task logs to the terminal as separated chunks separated by task.',
    src: '/images/blog/turbo-1-11-0/log-order-groups-light.png',
    props: {
      width: 682,
      height: 746.5,
      className: 'dark:hidden block rounded-xl',
    },
  }}
  dark={{
    alt: 'Using `--log-order=grouped` to output task logs to the terminal as separated chunks separated by task.',
    src: '/images/blog/turbo-1-11-0/log-order-groups-dark.png',
    props: {
      width: 682,
      height: 746.5,
      className: 'hidden dark:block rounded-xl',
    },
  }}
/>

Enable this behavior using `--log-order=grouped`. [Check out the documentation](/docs/reference/run#--log-order-option) to learn more

## Updated examples

Our repository contains [`an examples directory`](https://github.com/vercel/turbo/tree/main/examples) with starter monorepos for your projects.

To get started with an example, run:

```bash title="Terminal"
# Two Next.js applications
npx create-turbo@latest
```

```bash title="Terminal"
# Next.js and Remix
npx create-turbo@latest -e kitchen-sink
```

```bash title="Terminal"
# Vue and Nuxt
npx create-turbo@latest -e with-vue-nuxt
```

We're putting a renewed effort towards ensuring our examples are kept up-to-date. Additionally, we've re-architected our examples to advocate for best practices in monorepos. For example:

- In-editor go-to-definition across packages
- Dependencies updated to latest versions
- Tooling like ESLint, Prettier, jest, and vitest pre-configured
- Hot-reloading across packages

[Use an example](/docs/getting-started/examples) to get started, or [browse the code directly](https://github.com/vercel/turbo/tree/main/examples) for more.

## Community

Since releasing [Turborepo 1.10](/blog/turbo-1-10-0) we've seen incredible adoption and community growth:

- [23.6k+ GitHub Stars](https://github.com/vercel/turbo)
- [1.8M+ weekly NPM downloads](https://www.npmjs.com/package/turbo)
- 206 years of compute time saved through [Remote Caching on Vercel](https://vercel.com/docs/concepts/monorepos/remote-caching)

Turborepo is the result of the combined work of all of its contributors, including our core team.

Thank you for your continued support, feedback, and collaboration to make Turborepo your build tool of choice.
