▸case-01 Our pull request builds are taking too long in GitHub Actions. I need a recommended pipeline configuration and action script that leverages impacted targets and remote cache sharing to minimize redundant test and build steps. | fail→fail | 19,817 | 16,159 | -18% | 1 | 1 | 0% | 3,309 | 3,327 | +1% | 0 | 0 | — |
▸case-02 I am scaffolding a fresh monorepo using Nx and want to establish a clean architectural layout separating core UI components, business logic, and API clients into distinct library types. Please outline the recommended library classification schema along with strict tagging rules for imports. | fail→fail | 20,235 | 12,926 | -36% | 1 | 1 | 0% | 3,889 | 2,994 | -23% | 0 | 0 | — |
▸case-03 We want our GitHub Actions workflow to run tests only on changed projects when a PR is opened against main. A team member suggested running 'nx run-many --target=test --all' on every pull request to ensure everything is checked. Provide the command for running target tests only on changed code in CI. | fail→fail | 6,376 | 5,397 | -15% | 1 | 1 | 0% | 1,213 | 1,425 | +17% | 0 | 0 | — |
▸case-04 In an Nx monorepo, developers are importing feature module logic directly into shared data-access libraries, causing circular dependencies. We want to configure ESLint rules to prevent data-access libraries from importing feature libraries. Should we use custom path aliases in tsconfig or configure @nx/enforce-module-boundaries in .eslintrc.json? | fail→pass | 10,665 | 11,620 | +9% | 1 | 1 | 0% | 2,081 | 2,763 | +33% | 0 | 0 | — |
▸case-05 We are organizing logic into distinct library types in our monorepo. We have reusable React button components, state management store definitions with API calls, pure utility helper functions, and full page views with routing. We are tempted to put components and helper functions together into a single 'common' library. Detail the four-tier library classification schema. | fail→fail | 18,059 | 15,079 | -17% | 1 | 1 | 0% | 3,097 | 3,323 | +7% | 0 | 0 | — |
▸case-06 We want to make sure build outputs like dist/packages/ header files and storybook artifacts are cached by Nx locally. Should we manually configure custom bash scripts to check folder modified timestamps, or configure targetDefaults in nx.json? | pass→fail | 9,878 | 8,589 | -13% | 1 | 1 | 0% | 1,815 | 1,970 | +9% | 0 | 0 | — |
▸case-07 Our team wants to share build cache outputs across developer machines and CI workers using Nx Cloud or self-hosted Nx cache. Someone suggested putting the local .nx/cache folder into git tracking. Explain how remote caching should be properly configured. | fail→pass | 15,833 | 14,354 | -9% | 1 | 1 | 0% | 2,714 | 2,957 | +9% | 0 | 0 | — |
▸case-08 We have multiple application domains (e.g., 'storefront' and 'admin') and multiple tiers ('app', 'data-access'). A developer suggests setting up separate tsconfig files per project domain instead of tagging projects in project.json. How should project boundaries and domain ownership be declared in Nx? | fail→pass | 14,373 | 10,810 | -25% | 1 | 1 | 0% | 2,727 | 2,600 | -5% | 0 | 0 | — |
▸case-09 Our frontend team wants to enforce consistency across all new UI libraries by automating boilerplate creation. They are planning to write a shell script that copies template files into packages/. What is the standard Nx pattern for code generation and workspace scaffolding? | pass→pass | 14,167 | 12,303 | -13% | 1 | 1 | 0% | 2,557 | 2,672 | +4% | 0 | 0 | — |
▸case-10 We have a legacy monorepo using npm workspaces with multiple React apps and Node services. The build scripts in package.json run scripts sequentially in every folder. We want to migrate this workspace to Nx without completely rewriting our project structure. How should we initiate this migration? | pass→pass | 14,391 | 13,227 | -8% | 1 | 1 | 0% | 2,564 | 2,364 | -8% | 0 | 0 | — |
▸case-11 We have a global database schema file in the root of our monorepo at 'prisma/schema.prisma'. When this file changes, we need the 'api' app and 'db-client' lib to re-run their build targets even if their own files were not modified. A developer suggested touching source files manually. How should global file dependencies be defined? | fail→fail | 12,151 | 11,321 | -7% | 1 | 1 | 0% | 2,249 | 2,499 | +11% | 0 | 0 | — |
▸case-12 When building our Angular application in Nx, the build target requires its dependent feature libraries to be built first. Should developers manually trigger builds on all child projects in order, or should task orchestration be handled declaratively? | fail→fail | 11,779 | 9,169 | -22% | 1 | 1 | 0% | 1,952 | 1,983 | +2% | 0 | 0 | — |
▸case-13 We are migrating package.json scripts to Nx targets. Some developers want to keep all build commands as plain npm scripts in package.json without project.json files. Explain how targets should be defined in Nx for full task pipeline features. | fail→fail | 17,110 | 18,816 | +10% | 1 | 1 | 0% | 3,110 | 3,701 | +19% | 0 | 0 | — |
▸case-14 A team lead wants to audit dependency cycles and understand how a shared utility library is consumed across 15 micro-frontends before performing a major refactor. What tool or command should be used to inspect the dependency graph? | pass→pass | 11,146 | 6,813 | -39% | 1 | 1 | 0% | 2,010 | 1,595 | -21% | 0 | 0 | — |
▸case-15 In our CI pipeline, running tests sequentially across 20 projects takes 45 minutes. A developer proposed running 20 parallel SSH jobs manually splitting project names by hardcoded lists. What is the recommended Nx approach to parallelizing and distributing workload across CI agents? | fail→fail | 12,407 | 13,075 | +5% | 1 | 1 | 0% | 2,067 | 2,626 | +27% | 0 | 0 | — |
▸case-16 A developer is getting an error: 'A project tagged with scope:shared may only depend on projects tagged with scope:shared'. They are attempting to import a utility function from an app package into a shared ui library. How should this dependency issue be resolved correctly? | fail→pass | 9,332 | 8,866 | -5% | 1 | 1 | 0% | 1,569 | 1,961 | +25% | 0 | 0 | — |
▸case-17 We need to generate 10 new micro-service libraries with identical ESLint, TypeScript, and Jest configs. Someone suggested creating a generator using node file system operations manually without Nx devkit utilities. What devkit functions should be used to create files and update workspace tree? | fail→fail | 14,762 | 10,741 | -27% | 1 | 1 | 0% | 2,777 | 2,613 | -6% | 0 | 0 | — |
▸case-18 Our team noticed that changing environment variable definitions in .env files is not triggering cache invalidation for nx build, causing stale builds in CI. How should runtime environment variables and global file patterns be declared in Nx cache inputs? | fail→pass | 17,196 | 12,022 | -30% | 1 | 1 | 0% | 2,545 | 2,773 | +9% | 0 | 0 | — |
▸case-19 We are setting up workspace-wide default settings for lint, test, and build targets across 30 projects. Should we repeat target configurations inside every project's project.json file? | fail→fail | 11,141 | 11,029 | -1% | 1 | 1 | 0% | 2,035 | 2,447 | +20% | 0 | 0 | — |
▸case-20 We are managing a monorepo built using Turborepo (turbo.json). We want to set up build caching and task dependencies between our packages using turbo's pipeline syntax. Provide a turbo.json configuration for build, lint, and test tasks. | pass→pass | 10,934 | 6,937 | -37% | 1 | 1 | 0% | 2,103 | 1,719 | -18% | 0 | 0 | — |
▸case-21 We use Lerna in independent versioning mode across 10 packages in a traditional repository without Nx integration. We need to release new semantic versions and publish packages to npm using lerna publish. Provide the configuration and commands for Lerna independent versioning. | pass→pass | 13,165 | 11,640 | -12% | 1 | 1 | 0% | 2,498 | 2,499 | +0% | 0 | 0 | — |
▸case-22 We have a single standalone Node.js Express application (not a monorepo). We want to optimize our Dockerfile using multi-stage builds to reduce image size and cache npm install layers. Provide an optimized Dockerfile for this standalone app. | pass→pass | 14,807 | 14,281 | -4% | 1 | 1 | 0% | 2,698 | 3,243 | +20% | 0 | 0 | — |