# monorepo Published articles for monorepo. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Migrating to a Mobile Monorepo for React Native DevFeed: [Migrating to a Mobile Monorepo for React Native]() Original publisher: [Read original article]() Author: Khan Academy Published: 2017-05-29T22:00:00Z Content type: tutorial Language: en Sources: [Khan Academy]() Topics: [monorepo](), [React Native](), [Mobile](), [Submodules](), [Android](), [iOS](), [pull-requests](), [Jenkins]() Tags: [also](), [android](), [engineering](), [ios](), [jenkins](), [mobile](), [monorepo](), [news](), [react-native](), [submodules]() ### AI overview Khan Academy describes moving its React Native-related iOS and Android repositories from separate repositories and submodules into a single mobile monorepo. The change was intended to reduce synchronization problems, coordinate bridge changes across platforms, make pull requests and reviews more coherent, and simplify verification between codebases. The article also outlines repository-merging steps and anticipated trade-offs. ### Source excerpt By Jared Forsyth Over the past few months, we've been adding some React Native to our existing iOS ... Read more ## Migrating a Large Flow Monorepo to TypeScript DevFeed: [Migrating a Large Flow Monorepo to TypeScript]() Original publisher: [Read original article]() Author: Shawn Walton, Software Engineer Published: 2026-08-04T00:00:00Z Content type: article Language: en Sources: [Yelp]() Topics: [monorepo](), [TypeScript](), [migration](), [repo](), [Code]() Tags: [coverage](), [integrity](), [migration](), [monorepo](), [open-source](), [rewrite](), [typescript]() ### AI overview Yelp describes its gradual migration of a large Flow monorepo to TypeScript. The team chose a package-by-package approach to preserve type-checking trust and type safety while Flow and TypeScript coexisted in production, using open-source conversion tooling, custom codemods, and manual fixes. ### Source excerpt In early 2017, Webcore selected Flow as Yelp's next-generation typechecker over TypeScript. At the time there was no clear frontrunner. Flow had better support for React, better performance, and a respectable repository of types for NPM packages in flow-typed. However, a few years later the landscape had shifted, and it became clear that TypeScript was emerging as the stronger choice. TypeScript's DefinitelyTyped repo had thousands more packages than flow-typed, and many more packages shipped with built-in TypeScript headers. TypeScript also proved to be more stable over time, and limited uptake in the wider JS community made finding tools and documentation... ## How to protect an npm package from supply chain attacks DevFeed: [How to protect an npm package from supply chain attacks]() Original publisher: [Read original article]() Author: Travis Turner (richardturner@evilmartians.com) Published: 2026-07-28T00:00:00Z Content type: tutorial Language: en Sources: [Evil Martians]() Topics: [npm](), [supply-chain-security](), [Security](), [ci](), [GitHub](), [Open Source]() Tags: [2026](), [ci](), [developer-community](), [dx](), [github](), [how-to](), [javascript](), [monorepo](), [npm](), [npm-packages](), [open-source](), [performance-scale](), [security](), [supply-chain](), [supply-chain-security]() ### AI overview This tutorial explains how to protect npm packages from supply chain attacks. It covers Trusted Publishers, publishing restrictions, organization-wide 2FA, GitHub tag controls, pinned CI actions, CI security linting, cooldowns for new versions, and staged-release approval. ### Source excerpt How to protect your npm package from being stolen in a supply chain attack and improve its position in security ratings ## Migrating from Apollo Tooling to GraphQL Codegen at Yelp DevFeed: [Migrating from Apollo Tooling to GraphQL Codegen at Yelp]() Original publisher: [Read original article]() Author: Igor Kusakov, Software Engineer Published: 2026-07-16T00:00:00Z Content type: article Language: en Sources: [Yelp]() Topics: [GraphQL](), [Code generation](), [migration](), [Tooling](), [React](), [TypeScript](), [monorepo]() Tags: [code-generation](), [deprecated](), [graphql](), [migrate](), [monorepo](), [react](), [tooling](), [typescript]() ### AI overview Yelp describes migrating its frontend React monorepo from deprecated Apollo Tooling to GraphQL Codegen for generating TypeScript definitions from GraphQL queries and the server schema. ### Source excerpt Introduction At Yelp, we rely heavily on GraphQL and Apollo for data loading in our frontend React monorepo. When a developer writes a GraphQL query or mutation inside a React component, the shape of the response is defined by the query itself -- but TypeScript has no way to know what that shape looks like at compile time. That's where code generation (codegen) comes in. We rely on codegen to read our queries and server schema, then produce TypeScript type definitions for every operation's input variables and output data. In our codebase, this looks like: src/components/UserProfile/ ├── UserProfile.tsx <- contains... ## How we built a Flutter-powered AI coffee shop DevFeed: [How we built a Flutter-powered AI coffee shop]() Original publisher: [Read original article]() Author: Craig Labenz Published: 2026-06-22T15:16:53Z Content type: article Language: en Sources: [Flutter - Medium]() Topics: [Flutter](), [Artificial Intelligence](), [Firebase](), [monorepo](), [Cloud](), [Deployment](), [Web](), [Android](), [iOS]() Tags: [a2ui](), [ai](), [android](), [app](), [apps](), [cloud](), [code](), [deployment](), [firebase](), [flutter](), [gemini](), [genuis](), [go](), [google](), [hosting](), [ios](), [monorepo](), [web]() ### AI overview The Flutter team describes building GenLatte, a coffee-shop demo that combined a Flutter app with Nano Banana for customized images and GenUI for dynamically generated, personalized questions. The system let visitors order coffee topped with an image of their happy place, and the demo was presented at Cloud Next and Google I/O. ### Source excerpt Dash sits on a coffee shop's checkout counter drinking a latte with the Flutter logo printed on top If you start giving away coffee, people will show up. The Flutter team had been trying for a while to find a way to put this principle to work with a demo that started with a Flutter app and ended with a hot, tasty beverage. The problem was how to make it more interesting, more personal than just taking orders and delivering. Coffee's cool, but it's not The One Thing You Definitely Remember from Google I/O cool. So what changed? Two new bits of tech arrived on scene. One is Nano Banana, with its ability to quickly generate customized images. The second is GenUI, with its ability to generate UX dynamically at runtime and offer attendees personally tailored questions about how they'd like to modify those images. Put the two together with Flutter and you can offer folks the chance to order coffee with an image of their happy place printed on top with an inkjet printer. Now that's pretty memorable. All we had to do was execute. Twice, as it turned out -- the demo was called "GenLatte" at Cloud Next and "Antigravity Coffee Co." at Google I/O. For simplicity and to save a few tokens for the agent summarizing this article for you, the name "GenLatte" is used below. We built a coffee shop Realizing a vision as ambitious as GenLatte involves a lot of people. Like, a lot of people. There are teams to spec out the physical space and decide how "customers" [1] will flow. There are branding and concept teams to create the aesthetic. There are of course construction teams to go to the hardware store and buy lumber. Eventually, there's also the software engineers slapping code together to build the various apps, which is where I happened to come in. This blog post will only outline the software, but that is not to minimize the incredible work that went into the many other layers required for GenLatte to eventually open its doors. [1] Are they still customers if you don't charge anyth ## How Stripe Selectively Executes Tests in a 50-Million-Line Ruby Monorepo DevFeed: [How Stripe Selectively Executes Tests in a 50-Million-Line Ruby Monorepo]() Original publisher: [Read original article]() Author: Alexandre Zajac Published: 2026-06-08T15:30:11Z Content type: article Language: en Sources: [Hungry Minds]() Topics: [stripe](), [Software Engineering](), [Ruby](), [C++]() Tags: [c-plus-plus](), [dependencies](), [monorepo](), [performance](), [ruby](), [stripe]() ### AI overview Stripe built Selective Test Execution to run only the tests affected by changes in its 50-million-line Ruby monorepo. The system uses runtime file-access interception, dependency indexes, and guardrails to reduce test execution while maintaining code-safety confidence. ### Source excerpt PLUS: Index design fundamentals 👨💻, KV performance tool ⚡, Null bugs cost billions 💰 ## How Shopify Built the Infrastructure Beneath Its Slack-Native River AI Agent DevFeed: [How Shopify Built the Infrastructure Beneath Its Slack-Native River AI Agent]() Original publisher: [Read original article]() Author: Burke Libbey Published: 2026-05-28T12:30:02Z Content type: opinion Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [AI Agent](), [Slack](), [monorepo](), [Nix](), [Development](), [pull-requests]() Tags: [agent](), [ai-agent](), [ai-coding](), [cache](), [monorepo](), [slack](), [test]() ### AI overview Shopify describes how it built River, an AI agent that operates in company Slack, and the infrastructure choices that supported it. The article covers Shopify's move to a monorepo, adoption of Nix for reproducible environments, and the resulting changes to CI, merge queues, build caching, testing, and repository navigation. ### Source excerpt What it took to ship our Slack-native agent River, lessons learned, and the substrate that runs beneath it. Co-authored by River. ## From Co-Pilot to Full Automation: How Wix Is Embedding AI Agents Across an Engineering Org at Scale DevFeed: [From Co-Pilot to Full Automation: How Wix Is Embedding AI Agents Across an Engineering Org at Scale]() Original publisher: [Read original article]() Author: Wix Engineering Published: 2026-05-20T07:28:09Z Content type: article Language: en Sources: [Wix Engineering]() Topics: [ai-coding](), [agentic-coding](), [monorepo](), [Microservices](), [Claude](), [codex](), [cursor](), [GitHub Copilot](), [OpenClaw]() Tags: [agentic-coding](), [agents](), [ai](), [ai-coding](), [claude-code](), [codex](), [coding-agents](), [cursor](), [github-copilot](), [microservices](), [monorepo](), [openclaw]() ### AI overview Wix describes how agentic coding can be organized across an engineering organization with more than 2,500 microservices, thousands of engineers, strong service boundaries, and a large monorepo. The article presents a three-tier spectrum of cloud agents, coding agents or harnesses, and agents with computer access, identifying the harness tier as the practical sweet spot for software development as of 2025-2026. ### Source excerpt When you have over 2,500 microservices and thousands of engineers working across a massive multi-product platform, "just use AI coding tools" is not a strategy. It's a starting point - and not a particularly useful one. The question we kept coming back to at Wix wasn't whether to adopt AI in our engineering workflow. That ship had sailed. The question was: what does agentic coding actually look like when you have strong domain boundaries between services, a monorepo with years of... ## Optimizing Our Build Times by Migrating from Webpack to Rspack DevFeed: [Optimizing Our Build Times by Migrating from Webpack to Rspack]() Original publisher: [Read original article]() Author: Benson Pan, Software Engineer Published: 2026-05-20T00:00:00Z Content type: tutorial Language: en Sources: [Yelp]() Topics: [Webpack](), [build times](), [monorepo](), [build performance](), [Developer experience]() Tags: [build](), [build-times](), [build-tools](), [developer-experience](), [migration-guide](), [monorepo](), [performance](), [speed](), [tooling](), [tools](), [webpack]() ### AI overview A Yelp engineering blog post explains how the team migrated monorepo builds from Webpack to Rspack. It reports an approximately 50% reduction in build time and discusses compatibility, configuration, custom plugins, and a staged rollout. ### Source excerpt Over the years, Webpack has remained the bundler of choice for many JS projects, including here at Yelp. While it has served us well, its speed has increasingly become a bottleneck as our monorepo continues to grow. Fortunately, a bunch of new build tools (Vite, Parcel, Rspack, etc.) have emerged in recent years. Each of these tools promises different ways of improving performance and developer experience. In this blog post, we'll walk through how we migrated our monorepo builds from Webpack to Rspack and achieved an approximately 50% reduction in build time. Why Rspack Our team has been closely observing... ## Apollo Federation Goes Full Rust DevFeed: [Apollo Federation Goes Full Rust]() Original publisher: [Read original article]() Author: David Walter Published: 2026-05-07T17:50:09Z Content type: article Language: en Sources: [Apollo Blog]() Topics: [Rust](), [JavaScript](), [monorepo]() Tags: [announcement](), [apollo-federation](), [monorepo](), [performance](), [preview](), [rust]() ### AI overview Apollo Federation is releasing a preview of Rust-native composition. The Rust implementation is reported to be roughly 27x faster at the median, 8.5x faster at p95, and 6x faster at p99 across production graphs, while unifying the query planner and composition engine in one Rust monorepo. ### Source excerpt Rust-native composition for Apollo Federation is in preview: 27x faster at the median, unified codebase. Enable Federation Next in GraphOS Studio. ## Agentic Nx Import: Let an Agent Drive Your Monorepo Migrations DevFeed: [Agentic Nx Import: Let an Agent Drive Your Monorepo Migrations]() Original publisher: [Read original article]() Author: Juri Strumpflohner Published: 2026-04-30T00:00:00Z Content type: article Language: en Sources: [Juri Strumpflohner]() Topics: [AI Agent](), [Command-line interface](), [Tooling]() Tags: [agent](), [agentic](), [ai](), [ai-agent](), [ai-agents](), [blog](), [cli](), [code](), [git](), [import](), [migrations](), [monorepo](), [nx](), [project](), [skills](), [tests](), [token-efficiency](), [tool](), [verification](), [video]() ### AI overview The article describes an agentic workflow for importing existing projects into an Nx monorepo. The Nx CLI handles deterministic work such as cloning, file moves, plugin detection, setup, and Git history preservation, while an AI agent addresses workspace-specific gaps and performs follow-up verification. ### Source excerpt AI agents make importing existing projects into an Nx monorepo easier: does the heavy lifting while the agent handles workspace-specific gaps. ## Deploying a PNPM Monorepo to Cloudflare Pages DevFeed: [Deploying a PNPM Monorepo to Cloudflare Pages]() Original publisher: [Read original article]() Author: Juri Strumpflohner Published: 2026-04-21T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Cloudflare](), [monorepo](), [GitHub](), [GitHub Actions](), [Deployment](), [hosting](), [Cache]() Tags: [cache](), [ci](), [cloudflare](), [deployment](), [github](), [github-actions](), [hosting](), [monorepo](), [npm](), [nx](), [pnpm](), [workflow]() ### AI overview This tutorial explains how to deploy multiple apps from a pnpm or npm monorepo to Cloudflare Pages using Nx and one generic GitHub Actions workflow. Nx uses the project graph to identify affected apps, while caching avoids unnecessary rebuilds and redeployments. ### Source excerpt Deploy apps from a pnpm or npm workspace to Cloudflare Pages with one GitHub Actions workflow, using Nx as the task scheduler to rebuild only what changed. ## Sharing Tailwind CSS Styles Across Apps in a PNPM Workspaces Nx Monorepo DevFeed: [Sharing Tailwind CSS Styles Across Apps in a PNPM Workspaces Nx Monorepo]() Original publisher: [Read original article]() Author: Juri Strumpflohner Published: 2026-04-10T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Tailwind CSS](), [monorepo](), [Web Development](), [CSS]() Tags: [design](), [how-to](), [monorepo](), [npm-workspaces](), [nx](), [pnpm](), [sync-generators](), [tailwind](), [tailwind-css](), [tokens]() ### AI overview A tutorial on sharing Tailwind v4 design tokens across multiple applications in a pnpm or npm workspaces monorepo. It explains how to place shared CSS in a package, consume it from applications, and use Nx sync generators to automate Tailwind source directives based on project dependencies. ### Source excerpt Share Tailwind v4 design tokens across multiple apps in a pnpm + Nx monorepo using a shared styles package and automated @source directives. ## Docusaurus 3.10 DevFeed: [Docusaurus 3.10]() Original publisher: [Read original article]() Author: Sébastien Lorber Published: 2026-04-07T00:00:00Z Content type: release Language: en Sources: [Docusaurus Blog]() Topics: [releases](), [Documentation](), [Security](), [supply chain attacks](), [GitHub Actions](), [MDX](), [npm](), [OpenID connect (OIDC)](), [upgrade](), [monorepo](), [pnpm]() Tags: [github-actions](), [mdx](), [monorepo](), [npm](), [oidc](), [pnpm](), [release](), [security](), [supply-chain-attacks](), [upgrade]() ### AI overview Docusaurus 3.10 is the final release in the v3.x line and prepares sites for Docusaurus v4. It introduces future flags for upcoming breaking changes, makes Docusaurus Faster stable, and adds supply-chain security measures including npm Trusted Publishing, OIDC-based GitHub Actions releases, provenance records, and dependency checks. ### Source excerpt We are happy to announce Docusaurus 3.10. ## Resource Names for Enterprise TypeScript Monorepos DevFeed: [Resource Names for Enterprise TypeScript Monorepos]() Original publisher: [Read original article]() Author: Robin Wieruch Published: 2026-03-30T06:50:46Z Content type: tutorial Language: en Sources: [Robin Wieruch]() Topics: [TypeScript](), [Code](), [Structured-data]() Tags: [api-design](), [code](), [consistency](), [enterprise](), [monorepo](), [monorepo-resource-id](), [resource-oriented-design-typescript](), [typescript](), [typescript-resource-names](), [utilities]() ### AI overview This tutorial explains how to standardize resource names in multi-service TypeScript monorepos. It presents hierarchical resource naming, based on the Google API Design Guide, as a shared convention that replaces ad hoc string interpolation and supports consistent encoding and decoding across services. ### Source excerpt How to bring consistency to multi-service TypeScript applications by treating resource names and resource types as first-class concepts with shared utilities ... ## Five Claude Code Features for More Efficient Development DevFeed: [Five Claude Code Features for More Efficient Development]() Original publisher: [Read original article]() Author: Daniel Moka Published: 2026-03-23T06:44:01Z Content type: tutorial Language: en Sources: [Craft Better Software]() Topics: [Claude Code](), [coding](), [monorepo]() Tags: [claude-code](), [developer](), [javascript](), [monorepo](), [productivity](), [python](), [rust]() ### AI overview A practical guide to using five Claude Code features beyond basic prompting, including nested CLAUDE.md files and skills for repeatable workflows. It draws on the author's experience with production Rust, Python, and JavaScript codebases. ### Source excerpt 5 Claude Features That 10x Your Productivity ## Modernizing the Command Line: Heroku CLI v11 DevFeed: [Modernizing the Command Line: Heroku CLI v11]() Original publisher: [Read original article]() Author: Eric Black Published: 2026-03-19T22:29:49Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [Command-line interface](), [ECMAScript](), [modules](), [migration](), [maintenance](), [Usability]() Tags: [cli](), [command-line](), [heroku](), [javascript](), [legacy](), [maintainability](), [migration](), [modules](), [monorepo](), [news](), [node-js](), [npm](), [performance](), [release](), [upgrade](), [usability]() ### AI overview Heroku CLI v11 is available with a migration to ECMAScript Modules and oclif v4. The release also changes the build system from Yarn to npm, removes the monorepo structure, improves command execution and manifest caching, and adds semantic colors and theme support. ### Source excerpt Heroku CLI v11 is now available. This release represents the most significant architectural overhaul in years, completing our migration to ECMAScript Modules (ESM) and oclif v4. This modernization brings faster performance, a new semantic color system, and aligns the CLI with modern JavaScript standards. While v11 introduces breaking changes to legacy namespaces, the benefits are [...] The post Modernizing the Command Line: Heroku CLI v11 appeared first on Heroku. ## Monorepo Development: Common Objections, Scaling, and Team Independence DevFeed: [Monorepo Development: Common Objections, Scaling, and Team Independence]() Original publisher: [Read original article]() Author: Victor Savkin Published: 2026-02-24T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Development](), [Tooling](), [ci](), [Caching](), [Software Engineering]() Tags: [caching](), [ci](), [content](), [monorepo](), [nx](), [tooling]() ### AI overview This article explains common objections to monorepos and describes how a proper setup can support multiple projects and teams. Using Nx as an example, it covers affected-project testing and builds, remote caching, scalable CI pipelines, and team independence. ### Source excerpt Common objections to monorepos debunked: they are not monoliths, they scale, and they work great with AI. ## Why Monorepos Matter for Teams Using AI Coding Assistants DevFeed: [Why Monorepos Matter for Teams Using AI Coding Assistants]() Original publisher: [Read original article]() Author: Jeff Cross Published: 2026-02-18T00:00:00Z Content type: article Language: en Sources: [Juri Strumpflohner]() Topics: [monorepo](), [ai-coding](), [Tooling](), [Artificial Intelligence]() Tags: [ai](), [ai-coding](), [monorepo](), [tooling](), [webinar]() ### AI overview This article promotes a webinar about monorepo architecture, modern monorepo tooling, and how these tools may address coordination challenges for teams using AI coding assistants. It also presents monorepos as a potential way to improve development velocity. ### Source excerpt Monorepo architecture has evolved significantly in the past few years, yet the landscape remains confusing with inconsistent definitions, rapidly changing tooling, and implementation patterns that vary wildly across organizations. Meanwhile, teams adopting AI coding assistants are discovering that modern monorepo tooling is uniquely suited to solve the exact coordination challenges they're now facing. ## An Experiment in Agent Orchestration at Mintlify DevFeed: [An Experiment in Agent Orchestration at Mintlify]() Original publisher: [Read original article]() Author: Kathryn Lawrence Published: 2026-02-03T00:00:00Z Content type: opinion Language: en Sources: [Mintlify Blog]() Topics: [agent orchestration](), [Claude](), [Claude Code](), [Development](), [React](), [Storybook](), [Tailwind CSS](), [monorepo]() Tags: [agent-orchestration](), [ai-agent](), [claude](), [claude-code](), [development](), [engineering](), [monorepo](), [react](), [storybook](), [tailwind]() ### AI overview Mintlify describes an experiment using agent orchestration and AI coding tools while migrating its internal component system. The article concludes that an army of Claude agents was still no match for one human collaborator, Dmytro. ### Source excerpt TL;DR: We tried agent orchestration, but an army of Claudes is still no match for one Dmytro. ## Why I'm Seeking Sponsors for Metro, a Kotlin Dependency Injection Compiler DevFeed: [Why I'm Seeking Sponsors for Metro, a Kotlin Dependency Injection Compiler]() Original publisher: [Read original article]() Author: Zac Sweers Published: 2026-01-29T15:56:29Z Content type: opinion Language: en Sources: [Zac Sweers]() Topics: [Compiler](), [Dependency injection](), [build performance](), [build times](), [Kotlin](), [Mobile](), [monorepo]() Tags: [android](), [build-performance](), [build-times](), [compiler](), [dependency-injection](), [developer-productivity](), [kotlin](), [metro](), [monorepo](), [open-source]() ### AI overview The author discusses opening GitHub sponsorship for Metro, a Kotlin dependency injection project. They report build-performance gains, benchmark results against Dagger, compatibility across Kotlin and IDE versions, and adoption by several engineering teams. ### Source excerpt Metro is the proudest work of my career. Ever since starting it on vacation in November 2024, building it has been an incredible journey and the community reception has been nothing short of wonderful. It sits at the intersection of several fields I've come to specialize in, ranging ## How Caseware Unified 700+ Projects in an Nx Monorepo DevFeed: [How Caseware Unified 700+ Projects in an Nx Monorepo]() Original publisher: [Read original article]() Author: Philip Fulcher Published: 2026-01-16T00:00:00Z Content type: article Language: en Sources: [Juri Strumpflohner]() Topics: [Platform Engineering](), [Development](), [Angular](), [migration](), [Code quality]() Tags: [angular](), [cache](), [code-quality](), [customer-story](), [migration](), [monorepo](), [platform-engineering]() ### AI overview This case study describes how Caseware consolidated more than 700 projects into a unified monorepo using Nx. Its platform engineering team began with shared Angular libraries in a frontend monorepo, then incrementally moved backend applications into the shared workspace. The supplied summary reports a 93% cache hit rate and 181 days of compute saved weekly. ### Source excerpt Discover how Caseware unified 700+ projects into one monorepo, achieved a 93% cache hit rate, and saves 181 days of compute weekly with the Nx platform. ## Configure Tailwind v4 with Angular in an Nx Monorepo DevFeed: [Configure Tailwind v4 with Angular in an Nx Monorepo]() Original publisher: [Read original article]() Author: Juri Strumpflohner Published: 2026-01-14T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Tailwind CSS](), [Angular](), [monorepo](), [PostCSS](), [Web Development]() Tags: [angular](), [css](), [generators](), [how-to](), [monorepo](), [nx](), [sync](), [sync-generators](), [tailwind](), [tailwind-css]() ### AI overview A tutorial on configuring Tailwind CSS v4 with Angular in an Nx monorepo. It explains how Angular's PostCSS setup can scan the workspace broadly and produce bloated production CSS, then presents @source directives and Nx Sync Generators as ways to limit scanning and manage library dependencies. ### Source excerpt Learn how Tailwind CSS v4 scanning works with Angular in Nx monorepos, why you may have bloated CSS, and how to optimize it with @source directives and Nx Sync Generators. ## App Hosting adds support for Turborepo DevFeed: [App Hosting adds support for Turborepo]() Original publisher: [Read original article]() Author: Julia Reid Published: 2026-01-08T00:00:00Z Content type: release Language: en Sources: [Firebase Blog]() Topics: [Continuous Deployment (CD)](), [CI/CD](), [JavaScript](), [TypeScript](), [Next.js]() Tags: [app-hosting](), [continuous-deployment](), [dependencies](), [deployment](), [firebase](), [javascript](), [monorepo](), [next-js](), [parallel](), [typescript](), [web]() ### AI overview Firebase App Hosting now supports Turborepo for JavaScript and TypeScript monorepos. The article explains how Turborepo uses task configuration, dependency graphs, and parallel execution to support reliable and efficient builds and deployments. ### Source excerpt Efficient builds in App Hosting's continuous deployment pipeline, even for large and complex monorepos. [Next page]()