-
Notifications
You must be signed in to change notification settings - Fork 657
Closed
Labels
enhancementThe issue is asking for a new feature or design changeThe issue is asking for a new feature or design change
Description
Summary
I'm trying to run api-extractor on a repository with TypeScript 5.3 as a dev dependency. It was previously working with TypeScript 5.2.
Repro steps
See typescript-eslint/typescript-eslint#7821:
- Check out that PR branch & commit
yarnyarn build(specifically, thepackages/ast-spectask)
Expected result: Successful API extraction / build?
Actual result:
packages/ast-spec $ yarn build
api-extractor 7.38.0 - https://api-extractor.com/
Using configuration from ./api-extractor.json
Analysis will use the bundled TypeScript version 5.3.0-beta
ERROR: ts.getResolvedModule is not a function
packages/ast-spec $
Details
I'm guessing this is because of the (ts as any).getResolvedModule used to access TypeScript compiler internals:
rushstack/apps/api-extractor/src/analyzer/TypeScriptInternals.ts
Lines 89 to 92 in 4f15a3c
| // Compiler internal: | |
| // https://github.com/microsoft/TypeScript/blob/v4.7.2/src/compiler/utilities.ts#L161 | |
| return (ts as any).getResolvedModule(sourceFile, moduleNameText, mode); |
microsoft/TypeScript#55790 removed that internal API.
Standard questions
Please answer these questions to help us investigate your issue more quickly:
| Question | Answer |
|---|---|
@microsoft/api-extractor version? |
Both 3.6.1 and 3.8.0 |
| Operating system? | Mac |
| API Extractor scenario? | rollups (.d.ts) |
| Would you consider contributing a PR? | Yes |
| TypeScript compiler version? | 5.3.0-beta |
Node.js version (node -v)? |
20 (n/a) |
Metadata
Metadata
Assignees
Labels
enhancementThe issue is asking for a new feature or design changeThe issue is asking for a new feature or design change
Type
Projects
Status
Closed