You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running API Extractor for each library separately in the monorepo, to my surprise, in the API report of certain library I get full declarations of the types that were imported from my other libraries. For example the report for a certain library looks like this:
// Note: X was just imported from @my/other-libraryinterfaceX{foo: number;bar: string;}exportinterfaceYextendsX{ ... }
Instead, I would rather expect getting in the report just import { X } from '@my/other-library' when X comes from other library than I'm currently analyzing. For example I would expect the following report:
(similar as if X would be imported from some node_modules package).
It would be great to just output import { X } from '@my/other-library' in the report.
Note: I'm using a tsconfig with paths mapping to dist folders of other libraries (like "@my/other-library": ["dist/other-library"]") and I'm running API Extractor for each library on their ready precompiled dist d.ts files.
Note: I asked similar question previously in another issue. But now I'm creating a standalone Feature Request.
Standard questions
Please answer these questions to help us investigate your issue more quickly:
Question
Answer
@microsoft/api-extractor version?
7.12.0
Operating system?
Mac
API Extractor scenario?
reporting (.api.md)
Would you consider contributing a PR?
Yes, if only I kenw how to implement it 😉
TypeScript compiler version?
Node.js version (node -v)?
The text was updated successfully, but these errors were encountered:
When running API Extractor for each library separately in the monorepo, to my surprise, in the API report of certain library I get full declarations of the types that were imported from my other libraries. For example the report for a certain library looks like this:
Instead, I would rather expect getting in the report just
import { X } from '@my/other-library'
when X comes from other library than I'm currently analyzing. For example I would expect the following report:(similar as if
X
would be imported from somenode_modules
package).It would be great to just output
import { X } from '@my/other-library'
in the report.Note: I'm using a
tsconfig
withpaths
mapping to dist folders of other libraries (like"@my/other-library": ["dist/other-library"]"
) and I'm running API Extractor for each library on their ready precompiled distd.ts
files.Note: I asked similar question previously in another issue. But now I'm creating a standalone Feature Request.
Standard questions
Please answer these questions to help us investigate your issue more quickly:
@microsoft/api-extractor
version?node -v
)?The text was updated successfully, but these errors were encountered: