[infra] Restructured tsconfig files

[brijeshb42]

All apps/packages now extend a common tsconfig.options.json and only add project specific changes in their own configs.

Removed tsconfig.build.json in code-infra since there is no build step there.

[mui-bot]

Bundle size report

Bundle	Parsed size	Gzip size
@base-ui-components/react	0B(0.00%)	0B(0.00%)
@mui/x-charts-pro	0B(0.00%)	0B(0.00%)

Details of bundle changes

---

Check out the code infra dashboard for more information about this PR.

[Copilot]

Pull Request Overview

This PR restructures the TypeScript configuration files to follow a hierarchical approach. A new base configuration file tsconfig.options.json is introduced that contains common TypeScript compiler options, which is then extended by other configuration files to avoid duplication.

• Created a new base configuration file (tsconfig.options.json) with common TypeScript compiler options
• Replaced duplicated configurations across packages and apps with extends patterns
• Removed the redundant tsconfig.build.json file from the code-infra package

Reviewed Changes

Copilot reviewed 12 out of 14 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
tsconfig.options.json	New base configuration file with common TypeScript compiler options
tsconfig.js.json	New configuration extending base options for JavaScript-enabled projects
tsconfig.node.json	Simplified to extend tsconfig.js.json and added babel.config.* to includes
packages/docs-infra/tsconfig.json	Updated to extend tsconfig.options.json and removed redundant options
packages/code-infra/tsconfig.json	Simplified to extend tsconfig.js.json and updated includes
packages/code-infra/tsconfig.build.json	Removed as mentioned in PR description
packages/code-infra/src/cli/typescript.mjs	Added --declarationMap false flag to TypeScript command
packages/bundle-size-checker/tsconfig.json	Simplified to extend tsconfig.js.json
packages/babel-plugin-resolve-imports/tsconfig.json	Simplified to extend tsconfig.js.json
packages/babel-plugin-minify-errors/tsconfig.json	Simplified to extend tsconfig.js.json with updated includes
package.json	Added @types/babel__core dependency
apps/code-infra-dashboard/tsconfig.json	Simplified to extend tsconfig.options.json

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

[brijeshb42]

@Janpot Can I get a review on this ?

[Janpot]

When it comes to modularizing tsconfig, I'm not 100% convinced a deep hierarchy is the best solution. See this comment as a reason for allowing arrays in extends. The idea being that you create multiple base configs, each describing an aspect of the environment which you then can freely compose in your app/package configurations. I don't know how that should look exactly, but I'm thinking like e.g. our build tool can export its tsconfig that sets module resolution rules. Maybe we can make a config for when the target is node, and one for when it is browsers. Such that e.g. our node tools extend from ['tsconfig.node.json'] as they're not compiled, but docs-infra from ['tsconfig.browser.json', 'tsconfig.build.json']. In essence aiming at avoiding extending a tsconfig that itselfs also extends.
See also https://github.com/tsconfig/bases

[brijeshb42]

I am not sure I get what you are saying. Is it that there is tsconfig.options.json and tsconfig.js.json is extending it and then tsconfig.node.json is extending tsconfig.js.json? Both tcconfig.js.json and tsconfig.node.json should be standalone ?