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
In my project, I have libraries that generate types using vite-plugin-dts which uses underneath api-extractor.
When I migrated the tsconfig.json from moduleResolution: node to moduleResolution: bundler I realised that the output .d.ts was not identical.
Repro steps
The following repository is configured to use the api-extractor on the same code, but with 3 different moduleResolution: node, node16 and bundler.`
Summary
In my project, I have libraries that generate types using
vite-plugin-dts
which uses underneathapi-extractor
.When I migrated the
tsconfig.json
frommoduleResolution: node
tomoduleResolution: bundler
I realised that the output.d.ts
was not identical.Repro steps
The following repository is configured to use the
api-extractor
on the same code, but with 3 differentmoduleResolution
:node
,node16
andbundler
.`git clone [email protected]:Lukinoh/repro-api-extractor-bug
(Stackblitz)cd repro-api-extractor-bug
npm install
npm run build
dist
folders, it contains for eachmoduleResolution
:tsc
build.d.ts
The extracted
.d.ts
ofnode16
andbundler
are different fromnode
.I would have expected to have the content.
Expected result:
Actual result:
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: