Remove monorepo-wide tsconfig

[kachkaev]

🌟 What is the purpose of this PR?

This PR removes top-level tsconfig.json and moves tsconfig.base.json into a workspace named @local/tsconfig. Thus, all monorepo workspaces explicitly extend @local/tsconfig/block.json or @local/tsconfig/legacy-base-to-refactor.json. Dropping top-level tsconfig.json enables further improvements in the monorepo’s TSC / ESLint setup.

🔗 Related links

• Asana task (internal)

🚫 Blocked by

• Update ESLint and Playwright dependencies #1304
• Align eslintrc file names #1306
• Format .eslintrc.cjs files #1315

🔍 What does this change?

• @hashintel/tsconfig is moved from packages/hash/tsconfig to libs/javascript/@local/tsconfig and the workspace is renamed to @local/tsconfig. The plan is to move more workspaces to libs/javascript in the future, this is just a start.

• Each tsconfig.json file explicitly extends from @local/tsconfig.

• Each TypeScript workspace explicitly depends on @local/tsconfig and typescript, which ensures that dependency topology is accurate. This enables Yarn PnP and focused installs in the future.

• Workspace-specific ESlint configs are configured to use local tsconfig files in order to correctly apply @typescript-eslint/* rules.

• Bonus: Top-level yarn codegen is migrated to Turborepo for faster switches between branches. It is also possible to run yarn turbo run build if needed (although this is not used anywhere yet).

📜 Does this require a change to the docs?

• I’ve removed an out-of-date section on monorepo management.

⚠️ Known issues

• ESLint checks are still partially broken when it comes to comparing the results between CLI and the editor. This is because CLI narrow down the lists of files covered by ESLint. For example, packages/hash/frontend/next.config.js shows ESLint errors, but yarn lint:eslint does not fail because this script calls eslint --ext .js,.ts,.tsx ./src/. This is an inherited problem and its fix is out of this PR's scope.

🐾 Next steps

• Continue iterating on TSC config
• Continue iterating on ESLint config

🛡 What tests cover this?

• CI
• Update block metadata blockprotocol/blockprotocol#733
  Referring to @local/tsconfig to package.json files does not break yarn build in blocks.

❓ How to test this?

1. Check CI output

[codecov]

Codecov Report

Merging #1285 (d50f9fc) into main (aef4943) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##             main    #1285   +/-   ##
=======================================
  Coverage   40.01%   40.01%           
=======================================
  Files         320      320           
  Lines       16424    16424           
  Branches      819      819           
=======================================
  Hits         6572     6572           
  Misses       9847     9847           
  Partials        5        5           

Flag	Coverage Δ
backend-integration-tests	2.85% <ø> (ø)
unit-tests	1.15% <0.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
...pi/src/email/transporters/DummyEmailTransporter.ts	0.00% <0.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more