microsoft
WIP: [api-extractor] Upgrade bundled TypeScript to 5.5
Summary
Fixes #4805
Details
TypeScript release notes: https://devblogs.microsoft.com/typescript/announcing-typescript-5-5
- Upgrade TypeScript to
5.5.2 - Upgrade
@typescript-eslint/parserto7.14.1 - Adopt breaking changes of
typescript-eslint
How it was tested
Impacted documentation
Hi @iclanton, I failed to solve the lint and build error of this change. Would you please help me with it? Thanks
The issue is that the decoupled copies of the @rushstack/eslint-* packages are getting an old version of the @typescript-eslint/* packages. You should be able to fix this by patching those with the pnpm-config.json file or pnpmfile.
The issue is that the decoupled copies of the
@rushstack/eslint-*packages are getting an old version of the@typescript-eslint/*packages. You should be able to fix this by patching those with thepnpm-config.jsonfile or pnpmfile.
@iclanton I have temporarily postponed these issues by upgrading API Extractor's TypeScript version to 5.7.2. while rollingback the other projects across the repo to version 5.4.2. In this way, the API Extractor work can be merged separately from the repo upgrade work.
The test projects are all building without errors, although there were warnings for the Heft's TypeScript 2.9.x test project. I didn't dig too deeply into that one -- since @types/node today only supports 3.2+, I think it's probably time to drop support for 2.9.x and make 3.2.x our oldest supported version. But we can do that in a separate PR as well.