▸case-01 Our codebase is growing rapidly with over 15 packages, and our automated tests and builds take almost 30 minutes because every pull request rebuilds the entire workspace from scratch. Please outline a comprehensive performance optimization strategy detailing how to scope builds to changed packages and leverage caching. | fail→fail | 25,426 | 27,865 | +10% | 1 | 1 | 0% | 3,685 | 4,021 | +9% | 0 | 0 | — |
▸case-02 We are setting up a repository that contains several shared UI design system packages alongside three consumer web applications. Can you explain how to structure shared dependency management across workspace packages and outline a versioning and automated release workflow for publishing changed modules? | fail→fail | 20,529 | 23,674 | +15% | 1 | 1 | 0% | 3,689 | 3,890 | +5% | 0 | 0 | — |
▸case-03 I am maintaining a standalone single-package Node.js library stored in its own dedicated repository. How do I configure GitHub Actions to run npm publish when a git tag is pushed? | pass→pass | 11,697 | 9,822 | -16% | 1 | 1 | 0% | 2,309 | 2,143 | -7% | 0 | 0 | — |
▸case-04 We have microservices running in individual Docker containers deployed to Kubernetes. How do we configure Kubernetes horizontal pod autoscalers based on CPU utilization metrics? | pass→pass | 13,601 | 12,262 | -10% | 1 | 1 | 0% | 2,510 | 2,597 | +3% | 0 | 0 | — |
▸case-05 How do I center a div both horizontally and vertically inside a full-height web page container using modern CSS flexbox properties? | pass→pass | 8,639 | 4,602 | -47% | 1 | 1 | 0% | 1,720 | 1,061 | -38% | 0 | 0 | — |
▸case-06 In a JavaScript workspace with 10 internal sub-packages, developers keep installing different major versions of React across packages, causing multiple bundled instances at runtime. What exact workspace mechanism prevents inconsistent internal dependency versions across packages? | pass→pass | 17,209 | 11,642 | -32% | 1 | 1 | 0% | 2,867 | 2,273 | -21% | 0 | 0 | — |
▸case-07 Our CI pipeline runs pnpm test on all 20 workspace packages on every commit. We want to avoid re-testing unchanged packages across CI runs using remote cache storage. Provide a step-by-step strategy to configure remote caching and confirm cache hits. | pass→pass | 18,049 | 14,806 | -18% | 1 | 1 | 0% | 3,205 | 2,940 | -8% | 0 | 0 | — |
▸case-08 When running local development in a TypeScript multi-package repository, modifying sub-package A does not reflect in application B without manually rebuilding package A every time. How should package outputs and workspace protocol symlinks be set up for instant local feedback? | fail→pass | 18,833 | 14,577 | -23% | 1 | 1 | 0% | 3,404 | 2,859 | -16% | 0 | 0 | — |
▸case-09 We are planning a refactoring task that updates an internal core API package and 4 downstream consuming apps in a single Pull Request. How should PR verification be structured to ensure cross-package compatibility before merging? | fail→pass | 19,356 | 16,243 | -16% | 1 | 1 | 0% | 2,994 | 2,976 | -1% | 0 | 0 | — |
▸case-10 We have 5 independent Git repositories for various Node.js services and want to consolidate them into a unified workspace repo while preserving Git commit history. Outline the execution strategy and validation steps. | pass→pass | 19,090 | 15,137 | -21% | 1 | 1 | 0% | 3,349 | 3,109 | -7% | 0 | 0 | — |
▸case-11 We publish 6 public npm packages from our single repository. Developers frequently forget to update package versions or write changelogs when committing changes. What automated workflow forces developers to declare version bumps alongside code changes? | fail→fail | 13,311 | 11,401 | -14% | 1 | 1 | 0% | 2,379 | 2,232 | -6% | 0 | 0 | — |
▸case-12 Developers occasionally introduce circular dependencies between internal workspace packages (e.g., Package A imports Package B, which imports Package A), breaking builds unexpectedly. What tool and configuration detects this at build or lint time? | pass→pass | 15,998 | 13,072 | -18% | 1 | 1 | 0% | 2,793 | 2,590 | -7% | 0 | 0 | — |
▸case-13 In a multi-package repository, executing build at the root fails because downstream apps compile before their internal library dependencies finish building. How do we ensure execution order respects internal dependency order? | fail→pass | 12,979 | 10,658 | -18% | 1 | 1 | 0% | 2,209 | 2,088 | -5% | 0 | 0 | — |
▸case-14 We want to build a Docker container for only application-a located in apps/application-a inside our workspace, but docker build copies the entire 5GB workspace context. How do we create a minimal deployment bundle containing only application-a and its explicit internal dependencies? | fail→fail | 15,977 | 16,396 | +3% | 1 | 1 | 0% | 2,796 | 3,252 | +16% | 0 | 0 | — |
▸case-15 Each of our 12 packages has duplicate, slightly different tsconfig.json and ESLint configurations. How do we centralize and extend baseline developer tooling configs across all workspace packages? | fail→pass | 16,751 | 16,130 | -4% | 1 | 1 | 0% | 3,219 | 3,371 | +5% | 0 | 0 | — |
▸case-16 A developer imported code directly from apps/web/src/utils into packages/ui without declaring packages/ui in package.json dependencies. What enforcement strategy prevents undeclared cross-package imports? | fail→pass | 15,323 | 13,433 | -12% | 1 | 1 | 0% | 2,513 | 2,769 | +10% | 0 | 0 | — |
▸case-17 How should package.json at the workspace root be structured so running npm run test executes tests across all packages concurrently while providing clear failure logs? | fail→fail | 25,480 | 14,032 | -45% | 1 | 1 | 0% | 4,073 | 2,651 | -35% | 0 | 0 | — |
▸case-18 Our frontend app build output was served with stale API endpoints because the build tool cached previous build outputs even after REACT_APP_API_URL changed in CI. How do we explicitly declare environment variables as build cache inputs? | fail→pass | 15,426 | 10,629 | -31% | 1 | 1 | 0% | 2,184 | 2,241 | +3% | 0 | 0 | — |
▸case-19 We are combining a Go backend API service and a TypeScript React frontend into a single repository. How should root project configurations and workspace scripts accommodate multiple language toolchains? | fail→fail | 19,876 | 17,089 | -14% | 1 | 1 | 0% | 3,494 | 3,326 | -5% | 0 | 0 | — |
▸case-20 We want to run lint-staged on pre-commit hooks, but only check files that were modified within their respective workspace package scope. How should pre-commit hooks be configured for a multi-package workspace? | fail→pass | 19,748 | 13,656 | -31% | 1 | 1 | 0% | 3,403 | 2,741 | -19% | 0 | 0 | — |
▸case-21 A sub-package uses lodash at runtime despite lodash missing from its package.json dependencies because lodash is installed at the workspace root. How do we prevent phantom dependencies across packages? | pass→pass | 13,366 | 10,939 | -18% | 1 | 1 | 0% | 2,399 | 2,091 | -13% | 0 | 0 | — |
▸case-22 When publishing TypeScript packages internally within a workspace, consumer apps receive 'Cannot find module' or missing declaration errors. How should export fields in package.json be declared for TypeScript sub-packages? | pass→pass | 17,536 | 13,599 | -22% | 1 | 1 | 0% | 2,647 | 2,751 | +4% | 0 | 0 | — |