refactor: use tsup for building

[gao-sun]

Summary

for projects that do NOT need type declarations, tsup (or the underlying esbuild) is extremely faster than tsc. this is helpful for both dev and prod builds.

for type checks, eslint helps us do the job. we need to run tsc manually, added in #6355.

some known limits:

• if the project needs to emit type declarations, the performance usually stay the same between tsc and tsup
• cannot build esm tests with jest mocks (https://github.com/evanw/esbuild/issues/1921)

Testing

Performance

less than 1s vs. 10s

Accuracy

locally tested, also should be ok with the current ci

Checklist

• [ ] .changeset
• [ ] unit tests
• [ ] integration tests
• [ ] necessary TSDoc comments

[github-actions[bot]]

COMPARE TO master

Total Size Diff :chart_with_upwards_trend: +3.46 KB

Diff by File

|Name|Diff| |---|---| |package.json|:chart_with_upwards_trend: +22 Bytes| |packages/core/nodemon.json|:chart_with_upwards_trend: +384 Bytes| |packages/core/package.json|:chart_with_upwards_trend: +34 Bytes| |packages/core/tsconfig.base.json|:chart_with_upwards_trend: +215 Bytes| |packages/core/tsconfig.build.json|:chart_with_upwards_trend: +134 Bytes| |packages/core/tsconfig.json|:chart_with_upwards_trend: +222 Bytes| |packages/core/tsconfig.test.json|:chart_with_upwards_trend: +31 Bytes| |packages/core/tsup.config.ts|:chart_with_upwards_trend: +289 Bytes| |packages/core/tsup.dev.config.ts|:chart_with_upwards_trend: +284 Bytes| |packages/integration-tests/jest.setup.api.js|:chart_with_upwards_trend: +249 Bytes| |packages/integration-tests/package.json|:chart_with_upwards_trend: +26 Bytes| |packages/integration-tests/tsup.config.ts|:chart_with_upwards_trend: +258 Bytes| |packages/schemas/tsconfig.build.alterations.json|:chart_with_upwards_trend: +34 Bytes| |packages/schemas/tsconfig.build.gen.json|:chart_with_upwards_trend: +62 Bytes| |pnpm-lock.yaml|:chart_with_upwards_trend: +2.61 KB| |tsup.shared.config.ts|:chart_with_upwards_trend: +216 Bytes|