Sample work · Software & Web Apps
Monorepo: Workspace with shared configuration and validated dependencies
For a fictional company: a pnpm workspace with two packages that use each other via workspace references, with shared TypeScript, ESLint, and Prettier configuration. Dependencies are checked for cycles; nothing is installed.
Sample work (demo), not a client job. Built as a trial task with invented example data; the check figures below come from the automatic test run and are not polished.
What was built
- Two packages with workspace references, shared configuration
- Dependency graph checked for cycles
- Counter-test with cyclic dependency fails
- Repository is fictional
How it was checked
Automatic test run on 2026-10-31, taken from the log (test data invented, figures measured):
- Demo monorepo: 15 files, 2 packages with workspace:*-dependency, shared tsconfig/eslint/prettier, no cycles, no install
- 12 checks, counter-test fails
Limits
What this sample does not cover, so nobody expects more:
- Scaffold created as files only, not installed or built with pnpm; check version numbers during setup
- Refactoring an existing repo (history, CI) is a separate agreement
- A different scaffold is required for Nx or Turborepo
Something like this for your business?
Describe briefly what you need. You get a fixed price before I start; nothing happens without your yes.