-
-
Notifications
You must be signed in to change notification settings - Fork 416
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
chore: remove importsNotUsedAsValues
#4897
chore: remove importsNotUsedAsValues
#4897
Conversation
vue-component-meta
vue-component-type-helpers
@vue/language-core
@vue/language-plugin-pug
@vue/language-server
@vue/language-service
@vue/typescript-plugin
vue-tsc
commit: |
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.
Should we eventually aim for supporting verbatimModuleSyntax=true
? I've looked into it and there would be hundreds of necessary changes.
|
verbatimModuleSyntax
insteadverbatimModuleSyntax
This reverts commit 6d3620a.
verbatimModuleSyntax
importsNotUsedAsValues
This reverts commit 0d06c8d.
importsNotUsedAsValues
importsNotUsedAsValues
I've tried several times and the current conclusion is that verbatimModuleSyntax is not suitable for CJS projects. As an alternative to importsNotUsedAsValues, we need to use the equivalent ESLint rule in tsslint.config.ts. |
No description provided.