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
We wanna leverage stripping @internal APIs from rolluped dts definition by leveraging publicTrimmedFilePath config. Unfortunately things doesn't work as one would expect.
Actual
When TS Paths aliases are used, cross package type declarations are always inlined(bundled), although there is no bundledPackages being applied.
Expected
No matter if yarn workspaces/lerna/symlink resolution or TS path aliases is applied within monorepo to resolve absolute package paths, api-extractor should not inline(bundle) cross package type definitions.
Summary
We wanna leverage stripping
@internal
APIs from rolluped dts definition by leveragingpublicTrimmedFilePath
config. Unfortunately things doesn't work as one would expect.Actual
When TS Paths aliases are used, cross package type declarations are always inlined(bundled), although there is no
bundledPackages
being applied.Expected
No matter if yarn workspaces/lerna/symlink resolution or TS path aliases is applied within monorepo to resolve absolute package paths, api-extractor should not inline(bundle) cross package type definitions.
Repro steps
Link to whole repro
Steps:
yarn build
check
packages/one/dist/public.d.ts
:internalOne
has been stripped as expected (inside package API)Attributes
re-export hasn't been stripped (3rd party/node_modules package) - This should have been removed !- [api-extractor]:
@internal
APIs from 3rd party deps/node_modules are not removed in rolluped dts #3444check
packages/two/dist/public.d.ts
:internalOne
has been stripped as expected (re-export from a different within repo package API)Baseball
andHello
from@org/two
package (re-export from a different within repo package ) - should have been only re-export ofBaseball
!Details
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: