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
As a developer using vite-plugin-dts I would like to use TypeScript 5. In particular, I'd like to use moduleResolution: bundler, which was added in that release.
vite-plugin-dts currently uses "@microsoft/api-extractor. Unfortunately, this package comes with a specific version of TypeScript. At the time of wring, that version is ~4.8.4.
Suggested solution
if microsoft/rushstack#3891 on @microsoft/api-extractor is merged, then we, in theory, would be able to use any version of TypeScript. I'm unsure if additional code changes may be required in this repository. Unfortunately this PR looks stalled.
Alternative
It may be possible to stop using @microsoft/api-extractor and use the TypeScript API or CLI directly. In one project, I've worked around this by removing vite-plugin-dts and using tsc directly. This works for a basic vite build but not so nicely with vite build --watch.
Additional context
There is an overlap between this issue and #190, but I thought it was worth filing separately.
Description
As a developer using vite-plugin-dts I would like to use TypeScript 5. In particular, I'd like to use
moduleResolution: bundler
, which was added in that release.vite-plugin-dts currently uses
"@microsoft/api-extractor
. Unfortunately, this package comes with a specific version of TypeScript. At the time of wring, that version is~4.8.4
.Suggested solution
if microsoft/rushstack#3891 on
@microsoft/api-extractor
is merged, then we, in theory, would be able to use any version of TypeScript. I'm unsure if additional code changes may be required in this repository. Unfortunately this PR looks stalled.Alternative
It may be possible to stop using
@microsoft/api-extractor
and use the TypeScript API or CLI directly. In one project, I've worked around this by removing vite-plugin-dts and usingtsc
directly. This works for a basicvite build
but not so nicely withvite build --watch
.Additional context
There is an overlap between this issue and #190, but I thought it was worth filing separately.
Validations
The text was updated successfully, but these errors were encountered: