▸case-18 In a TypeScript monorepo, compiling each package independently causes high memory usage and slow build times because types are re-checked repeatedly across boundaries. What TypeScript feature solves cross-package build efficiency? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-02 We need a reliable automated release process for our open-source JavaScript library monorepo. Outline an actionable framework for managing cross-package version bumping, automated changelog generation, dependency linking, and release verification. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-10 We have shared utility functions used across three web apps in our repo. Should we copy-paste the utility files into each app directory, compile them into a shared npm package with TypeScript build outputs, or set up an internal workspace package? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-19 We want to run linting before git commits in a monorepo. Should lint-staged run eslint across the entire repo on every commit, or how should pre-commit hooks handle staged files across multiple packages? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-08 In our Node.js workspace, package A doesn't list package B in its package.json dependencies, but code in package A can still import package B because of flat node_modules hoisting. Developers keep accidentally using unlisted packages. How do we prevent this phantom dependency access? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-01 Build times in our monorepo CI pipeline have become extremely slow as new applications were added. Can you create a step-by-step optimization strategy that addresses build caching, selective task execution, and concrete steps to measure performance improvements? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-22 Multiple packages in our monorepo rely on nested third-party dependencies that contain a critical security vulnerability. How do we force all workspace packages to override and resolve a specific patched dependency version globally? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-17 How do developers document breaking changes or feature updates across multiple modified packages in a monorepo PR before merging into main, without manually updating version strings in package.json? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-14 Local build caching works great for developer machines in our monorepo, but CI builds start fresh and miss local cache hits. What caching layer architecture bridges developer machines and CI build agents? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-09 In a multi-package JavaScript repo, package-a needs to import package-b from the same repository. Should we publish package-b to npm registry after every change and install via npm version tags, or is there a standard workspace protocol for local linking? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-12 We manage 5 distinct packages in a single repo. Two are public SDKs and three are internal helper libraries. Should we force all 5 packages to share identical version numbers or use independent versioning? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-03 We have a single standalone Python web application in a dedicated git repository. Please configure a GitHub Actions workflow to run pytest on pull requests. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-13 Package A imports Package B, and Package B imports Package A in our monorepo workspace graph. Build tools throw topological sorting errors. What is the standard structural resolution for circular workspace dependencies? | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-04 Our single Golang microservice needs a Dockerfile for production deployment. Show how to write an optimized multi-stage Docker build for a single main.go executable. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-05 I am maintaining a single standalone npm package called express-logger-mini in its own repo. How do I configure package.json and run npm publish to publish it to the npm registry? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-11 When running CI on pull requests in a large monorepo with 40 packages, should we run tests on all 40 packages every time to be safe, or is there a mechanism to restrict execution? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-15 Package web-app depends on shared-ui, which depends on core-utils. If we run a build task across the monorepo, in what order must tasks execute, and how do build tools determine this? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-20 Should global developer tooling like Prettier, ESLint configs, and TypeScript base configurations be duplicated inside every package subdirectory or defined at the monorepo root? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-21 Developers in our frontend monorepo are importing internal private helper files directly from other packages using relative path navigation like '../../packages/ui/src/internal/secret.ts'. How do we enforce package export boundaries? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-06 We want to configure build task caching for our workspace applications. Should we configure the build task in the pipeline configuration to run independently with `dependsOn: []` across all packages in parallel to get maximum speed, or does `dependsOn: ["^build"]` need to be specified? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-07 In a multi-package JavaScript repository, should we list each sub-package path individually under the `workspaces` array in root `package.json` (such as `["packages/app1", "packages/app2", "packages/ui"]`), or use glob patterns like `["packages/*"]`? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-16 When building a Docker container for a single application inside a 20-package monorepo, we don't want to copy the entire monorepo root node_modules or source files into the Docker context. What strategy isolates the target app and its transitive workspace dependencies? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |