Better CI System

[black7375]

Distributed CI execution

It is divided into three parts.

1. Can be checked without building
   • Package constraints: Immutable, Peer Deps
   • Lint: Lint and formatting
2. Type Checking: Type checking requires some build. But you don't have to build everything.
   • Build for ESM only using tsc --build
   • Use options like emitDeclarationOnly and incremental
3. Build
   • For CI, we only test with ESM.
   • After checking if Type creation is not necessary, apply. If Type creation is found to be necessary, tasks 2 and 3 are combined.
   • Run tests based on build results. Not this time, but later we may try test sharding as well.

Caching

Leverage caching more aggressively with ESLint, Typescript, Vite, Turbo, etc.
The goal is to have caching in a single directory.

• ./.cache/
  • eslint
  • prettier/
  • typescript/
  • vite
  • turbo

[black7375]

We use eslint-plugin-prettier, which does not support cache option in JS API.

• https://github.com/prettier/eslint-plugin-prettier/blob/fa9607e92bdb63942c906d3a888fa6308ef9f7f9/worker.js#L179-L189
• https://github.com/prettier/prettier/blob/9282520e0e3f7997d19676dafd748797c42d1e0b/src/index.js#L67

This option is supported exclusively in CLI.

---

It looks like caching can be applied to resolveConfig as well.

[black7375]

Typescript project reference sync feature is still lacking.

• workspaces-to-typescript-project-references does not handle references to config files correctly azu/monorepo-utils#83

The local tsconfig.*.json* should be in sync with the project reference.