Turborepo 1.2: Excessive-performance obtain design for monorepos

Friday, April eighth, 2022

Since releasing Turborepo v1.1 in gradual January, now we have seen unbelievable adoption and community development:

• 6.5k+ GitHub Stars
• 140k+ weekly NPM downloads (doubling since our closing blog submit for v1.1)
• 95+ OSS contributors
• 900+ members of the Turborepo Community Discord
• 1.6 years of Time Saved by Faraway Caching on Vercel, saving bigger than 2.5 months a week

We have extra improved ergonomics, observability, and security with Turborepo v1.2 featuring:

• Original Job Filtering API: --filter provides extra expressive and intuitive job filtering capabilities to turbo urge
• Human-readable and JSON dry runs: --dry-urge flag can print out info a pair of turbo urge with out executing any initiatives, in both human and JSON-parse appropriate formats
• Improved Interior Scheduler and Graph: We refactored turbo ‘s interior scheduler and graph to be extra ergonomic and predictable
• Enhanced Faraway Cache Security: Cryptographically mark remote cache artifacts with your be pleased secret key

Replace at this time by running npm install turbo@latest. After running turbo urge for the first time, one can discover instructions about be taught how to spend @turbo/codemod to urge automatic migrations for v1.2.

Original Job Filtering API#

We are wrathful to open one of our most requested factors: the power to expressively filter initiatives by a --filter flag. The --filter flag is the grand extra grand successor to the latest combination of --scope, --encompass-dependencies, --since, and --no-deps flags.

With --filter that you may maybe well presumably repeat turbo to prohibit executing instructions to a subset of matched packages to your monorepo per title, folder, or even supposing it has modified since a git commit ref.

Secure a be taught about at some examples of what that you may maybe well presumably assassinate with the recent --filter remark:

• --filter= – match by accurate kit title or glob sample
• --filter=...– match by kit title/glob and encompass all dependent packages of suits
• --filter=...^– match by kit title/glob and encompass all dependent packages of suits, nonetheless exclude the suits themselves
• --filter=... – match by kit title/glob and encompass your total matched packages’ dependencies
• --filter=^... – match by kit title/glob and encompass all matched kit dependencies, nonetheless exclude the suits themselves
• --filter={./course/to/kit} – match by course or filesystem glob sample
• --filter=[origin/main] – match by modified packages since a git commit ref

You may maybe well maybe presumably spend a pair of filters together to obtain grand extra granular filtering in addition to combine each fragment of the above patterns {}, [] , ^ , and ... to insist extra advanced behavior.

As an illustration, whereas you had an app located in ./apps/web directory with local packages weak as dependencies, and a Turborepo pipeline the assign apart test depends upon ^obtain topologically, running:

turbo urge test --filter={./apps/web}[HEAD^1]^...

would repeat turbo to make certain dependencies are constructed and to urge the test script in all of the local dependencies of the app located in ./apps/web, now not including that app itself, if the app has modified since HEAD^1.

For extra well-known factors and examples, consult with the recent filtering documentation.

Debug and Automate with --dry-urge#

You may maybe well maybe presumably now see the impact of turbo urge with out genuinely executing any instructions by appending both --dry-urge or --dry-urge=json to any turbo urge remark. This may maybe well cease up in both human or JSON output.

Dry runs are extremely purposeful for 2 cases:

• Debugging and testing urge alternate choices
• Utilizing turbo filtering and job graphs for constructing automations

We hope that this can give a boost to visibility into what turbo is doing, speeding up debugging, and produce it more uncomplicated to leverage turbo in dynamic CI/CD systems.

Improved Interior Scheduler and Graph#

When the spend of turbo urge, every kit.json job is added to an interior graph to diagram dependencies per the inferred relationships defined to your Turborepo pipeline. This job graph enables Turborepo to efficiently time table incremental concurrent job running and cache job outputs for later spend.

We have gotten made most primary improvements to the interior job scheduler and resulting graph constructing, main to greater performance and a bigger developer ride. As an illustration, in many conditions, you will now not must spend --encompass-dependencies. As a change, after specifying your job entry factors, the recent and improved graph will mechanically take care of this graph decision to your behalf.

Cache Outputs Integrity and Signature Verification#

You may maybe well maybe presumably now configure Turborepo to mark remote cache outputs the spend of HMAC-SHA256 with a secret key before importing them to the Faraway Cache. When Turborepo downloads signed cache artifacts, it’ll now test the artifact’s integrity and authenticity. Any artifact that fails to test will be overlooked, discarded, and handled as a cache omit by Turborepo.

To enable this function, situation the remoteCache alternate choices to your turbo.json config file to encompass signature: correct. Then specify your secret key by declaring the TURBO_REMOTE_CACHE_SIGNATURE_KEY atmosphere variable.

{
  "$schema":  "[https://turborepo.org/schema.json](https://turborepo.org/schema.json)",
  "remoteCache":  {
    // Signifies if signature verifcation is enabled.
    "signature":  correct
  }
}

Other worm fixes and improvements#

• --sso-team flag now permits teams with SAML tokens to log in by turbo login with honest accurate team permissions
• --log-output flag helps you to manipulate what logs are printed to the terminal, and when, allowing you to level of interest handiest on what’s recent
• FORCE_COLOR atmosphere variable is now supported
• TURBO_FORCE=correct atmosphere variable will now force execution
• --remote-handiest and TURBO_REMOTE_ONLY=correct will repeat turbo to handiest spend Faraway Caching
• We now mask >>> FULL TURBO when there may maybe be now not lower than one job attempted
• Tale v2+ with Depart’n’Play (PnP linker) is supported for the turbo urge remark, nonetheless turbo prune is restful now not totally supported
• Fastened regression with chrome tracing if --profile is specified
• You may maybe well maybe presumably now situation concurrency by share of CPUs with --concurrency=50%

We’re hiring!#

The Turborepo team at Vercel is hiring! We’re as much as five core team members already this twelve months and must hire grand extra. We’re namely procuring for stout-time Senior Construct Programs Engineers.

What’s next?#

In conjunction with seamless incremental adoption/migration and speeding up CI/CD, now we have been specializing in making improvements to Turborepo’s day-to-day ergonomics, security, and observability. The recent --filter flag, signed artifacts, and dry runs are well-known steps towards those targets.

Subsequent up, we’ll be focusing an enhanced local constructing ride, codebase automations, and overall CLI performance.

Thank you, contributors#

Turborepo is the cease outcomes of the blended work of over 95 particular person developers and our core team.

This open used to be introduced to you by the contributions of: @gsoltis09, @jaredpalmer, @gaspar09, @shuding, @rajatkulkarni95, @VanTanev, @Kikobeats, @tknickman, @thebanjomatic, @chelkyl, @elado, @finn-orsini, @becca, @weyert, @ekosz