configed by tsconfig "alias", but treat with external dependency
Summary
already asked in the chat room, comfirmed that it's not supported now.
my tsconfig.json as below
"baseUrl": "./",
"paths": {
"@interface/*": ["src/interface/*"],
}
Expected result:
expert:
Actual result:
import { Foo } from '@interface/test'
export { Foo }
Details
seems api-extractor ignore those @interface declaration files, treating them as external deps.
I am searching inside the source code, but still don't know which module parse the AST and mark isExternal as true.
PS: Seems pnpm link and rush link doesn't support link monorepo/api-extractor to my demo (outside rushstack monorepo). So I run the dev mode by relative path: node ../../../rushatck/apps/api-extractor/lib/start.js. Is any better way to dev?
Standard questions
Please answer these questions to help us investigate your issue more quickly:
| Question |
Answer |
@microsoft/api-extractor version? |
^7.19.5 |
| Operating system? |
mac |
| API Extractor scenario? |
rollups (.d.ts) |
| Would you consider contributing a PR? |
Yes |
| TypeScript compiler version? |
4.4.3 |
Node.js version (node -v)? |
14.17.4 |
configed by tsconfig "alias", but treat with external dependency
Summary
already asked in the chat room, comfirmed that it's not supported now.
my tsconfig.json as below
Expected result:
expert:
Actual result:
Details
seems api-extractor ignore those @interface declaration files, treating them as external deps.
I am searching inside the source code, but still don't know which module parse the AST and mark
isExternalas true.PS: Seems pnpm link and rush link doesn't support link monorepo/api-extractor to my demo (outside rushstack monorepo). So I run the dev mode by relative path:
node ../../../rushatck/apps/api-extractor/lib/start.js. Is any better way to dev?Standard questions
Please answer these questions to help us investigate your issue more quickly:
@microsoft/api-extractorversion?node -v)?