-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(tsconfig): apply @vue/tsconfig
#729
Conversation
fde1022
to
8e2b465
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Blocking merge until I have time to dig into what is being proposed in this PR
Use an exported `const enum` in vite is forbidden due to the [compiler limitation](https://vitejs.dev/guide/features.html#isolatedmodules). To fix this, some `const enum` exports need to be reshape to `enum`. Besides the `const enum`, we also need to use the Type-Only Imports and Export syntax to avoid potential problems like type-only imports being incorrectly bundled. See https://vitejs.dev/guide/features.html#transpile-only These restrictions are all included in `@vue/tsconfig`, so we applied it to the root `tsconfig.json` to prevent further issues.
8e2b465
to
5940fe0
Compare
@vue/tsconfig
@vue/tsconfig
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Use an exported
const enum
in vite is forbidden due to the compiler limitation. To fix this, someconst enum
exports need to be reshape toenum
.Besides the
const enum
, we also need to use the Type-Only Imports and Export syntax to avoid potential problems like type-only imports being incorrectly bundled. See https://vitejs.dev/guide/features.html#transpile-onlyThese restrictions are all included in
@vue/tsconfig
, so we applied it to the roottsconfig.json
to prevent further issues.Summary
PR Checklist