Skip to content

registry: add turbo #8553

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jdx merged 1 commit into from
Mar 11, 2026
Merged

registry: add turbo #8553

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions registry/turbo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
backends = ["npm:turbo"]
description = "Turborepo is a high-performance build system for JavaScript and TypeScript codebases."
test = { cmd = "turbo --version", expected = "{{version}}" }
Comment on lines +1 to +3

@greptile-apps greptile-apps Bot Mar 11, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing detect field for turbo.json

Turborepo projects typically include a turbo.json configuration file at their root. Adding a detect field would allow mise to automatically activate this tool when users are inside a Turborepo project, consistent with how other tools like bun (which detects bun.lock, bun.lockb, bunfig.toml) handle project-level activation.

Suggested change
backends = ["npm:turbo"]
description = "Turborepo is a high-performance build system for JavaScript and TypeScript codebases."
test = { cmd = "turbo --version", expected = "{{version}}" }
backends = ["npm:turbo"]
description = "Turborepo is a high-performance build system for JavaScript and TypeScript codebases."
detect = ["turbo.json"]
test = { cmd = "turbo --version", expected = "{{version}}" }

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

@gemini-code-assist gemini-code-assist Bot Mar 11, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The test command turbo --version outputs a string that includes more than just the version number (e.g., @turbo/cli/1.13.3 darwin-arm64). The expected = "{{version}}" check will likely fail because it expects an exact match with the version string (e.g., 1.13.3).

To ensure the test passes, I recommend removing the expected field. The test will then simply verify that the command executes successfully (with a zero exit code), which is a sufficient check for a successful installation.

Suggested change
test = { cmd = "turbo --version", expected = "{{version}}" }
test = { cmd = "turbo --version" }

@igas igas Mar 11, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It does print:

$ turbo --version
 WARNING  No locally installed `turbo` found. Using version: 2.5.3.
2.5.3

But in the real example where turbo installed in the repo:

$ turbo --version
2.8.13

Loading