Turborepo
Turborepo is a build system optimization tool for JavaScript and TypeScript monorepos, serving development teams managing multiple packages.
About this data
Updated June 29, 2026
Overall Pulse Score
+36 over this period
A 0-100 index summarizing the tone of 290 relevant public mentions gathered from public online communities across 16 weeks in the selected period. It measures online sentiment, not a rating of the product's quality.
Weekly Sentiment Trend
Pulse Score by week over the selected period. Each point is one complete week of mentions.
This week in public discussion
Community discussion around Turborepo held steady over the recent period, with commenters frequently praising its monorepo orchestration capabilities, integration options, and build speed. Several mentions highlighted it as a go-to choice for consolidating tooling across workspaces. At the same time, a notable share of discussion centered on bugs and reliability concerns, including specific reports around turbo prune failures and OS-dependent cache behavior that commenters flagged as frustrating in cross-platform setups.
Read the deeper analysisAI-generated summary of public online discussion during this period. It reflects the tone of that discussion, not facts about the product or our views.
Sentiment mix by week
How the tone of public discussion splits each week.
Most-discussed praise
Most-discussed complaints
Themes across the selected period, with mention counts.
How Turborepo compares
Pulse Score over the selected period versus the top tracked competitors in Coding.
Where the mentions come from
Share of the 290 relevant public mentions in the selected period, by source.
Sample public mentions
Showing 5 of 290 analyzed public mentions in this period, with links to the original source. We do not reproduce full threads.
“Excessive disk usage and RAM growth caused by outputs: [".next/**"] in Turborepo config. I noticed severe performance issues when using the default Turborepo configuration with Next.js apps: Tracking the entire .next directory caused very high disk usage, RAM growth, and slower l...”
“turbo prune with certain deps fails to install on bun. ### Verify canary release - [x] I verified that the issue exists in the latest Turborepo canary release. Link to code that reproduces this issue https://github.com/JRoy/turbo-repro Which canary version will you have in your r...”
“Ctrl+C not crashing turbo dev. ### Verify canary release - [x] I verified that the issue exists in the latest Turborepo canary release. Link to code that reproduces this issue turbo dev Which canary version will you have in your reproduction? turbo 2.9.15-canary.5 Environment inf...”
“turbo query affected --tasks //#root-task --exit-code returns "not affected" even when input files changed. # turbo query affected --tasks //#root-task --exit-code returns "not affected" even when input files changed Summary turbo query affected --tasks //# always reports zero af...”
“Artifact path is OS-dependant, disabling cache reuse between platforms. ## 🐛 Bug Report The artifact key is generated using some variation of const artifactPath = join(team, artifactId), where the join function is path.join. This makes the resulting artifact location OS-dependen...”
285+ more analyzed mentions, full history, and theme breakdowns are part of Pro.
Get ProDeeper analysis
- Feature praise and performance appreciation dominated positive discussion, but bug reports were the single largest complaint theme across the window.
- Sentiment dropped sharply once mention volume grew in mid-May and then stayed flat in the low-to-mid fifties for the remainder of the period.
- Opinion was divided between commenters actively integrating Turborepo into production monorepo setups and those reporting reliability and cross-platform caching issues.
- The combination of stable scores and rising then sustained mention volume suggested a settled rather than improving sentiment picture by late June.
| Praise theme | Mentions |
|---|---|
| Strong features | 114 |
| Performance | 72 |
| Good integrations | 51 |
| Easy to use | 36 |
| Feels fast | 33 |
| Complaint theme | Mentions |
|---|---|
| Bugs | 60 |
| Reliability | 42 |
| Missing features | 16 |
| Performance | 10 |
| Feels slow | 3 |
Discussion around Turborepo over the past four weeks settled into a pattern that felt notably split, with praise themes numerically outweighing complaints but bug reports carrying enough weight to keep overall sentiment in a cautious middle range. Feature praise dominated the positive side of conversation, followed closely by performance appreciation, suggesting that when things work as expected, commenters tended to be genuinely enthusiastic about what the tool offers. Integration and ease of use also drew favorable mentions, with several discussions framing Turborepo as a natural fit for teams consolidating tooling inside monorepos.
The score trajectory tells a more complicated story about how sentiment evolved. Early in the window, mention volume was extremely low and scores were high, but those readings carry little weight given how few voices contributed. As discussion scaled up through mid-May into early June, scores dropped sharply and stabilized in the low-to-mid fifties, where they remained for the rest of the window. The plateau suggests that sentiment neither recovered nor worsened once the broader community weighed in, pointing to a persistent tension rather than a temporary dip.
Bugs were the single largest complaint theme by a wide margin, and sample mentions reinforced this, with commenters reporting failures tied to specific runtime environments, OS-dependent artifact paths breaking cross-platform cache reuse, and errors surfacing in canary builds. Reliability concerns followed closely, and together these two themes shaped a notable portion of the conversation's skeptical undercurrent.
Opinion appeared divided most sharply around whether Turborepo was ready to anchor serious infrastructure decisions. On one side, discussion suggested active adoption for shared config packages, documentation migrations, and architectural planning. On the other, the volume of bug reports relative to total mentions implied that a meaningful share of users were hitting friction in real workflows, not just edge cases.
AI-generated summary of public online discussion during this period. It reflects the tone of that discussion, not facts about the product or our views.
Member perspectives
Individual opinions from Pro members, posted over time. These are personal member views, not aggregated sentiment data.
Overall Pulse Score
+36 over this period
A 0-100 index summarizing the tone of 290 relevant public mentions gathered from public online communities across 16 weeks in the selected period. It measures online sentiment, not a rating of the product's quality.
Data summary
Compare with another tool
Turborepo
54
Trainual
88
Score-level preview from live weekly tracking.
Are you Turborepo?
Get a private enterprise dashboard for your product - full history, every source, theme deep-dives, and weekly alerts. You can also respond to the data shown here.
Explore the enterprise dashboardAffiliate disclosure
Some links on this site may be affiliate links. If you click one and make a purchase, we may earn a commission at no extra cost to you. Learn more.
Is Turborepo your product?
See everything behind this page - full history, every source, theme deep-dives, and weekly alerts - in a private enterprise dashboard.
Request early accessCompare with similar tools
Safari MCP Server
A Model Context Protocol server that gives AI assistants programmatic access to Safari browser automation for developers.
Free
View DetailsBubble
No-code platform that lets users design, build, and deploy full-stack web applications without writing code.
Free tier; paid plans available
View Details