-
Notifications
You must be signed in to change notification settings - Fork 92
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
Adds many unrelated vue dependencies to the project #361
Comments
Temporary workaround: in case project uses pnpm you can add next settings in {
"pnpm": {
"packageExtensions": {
"vite-plugin-dts": {
"dependenciesMeta": {
"@volar/typescript": {
"optional": true
},
"vue-tsc": {
"optional": true
},
"@vue/language-core": {
"optional": true
}
}
}
}
}
} |
Are you install the plugin to Those packages of Volar are the basic dependencies of the plugin, they are not optional. |
Let me be clear. It's not about final chunk. Such build time deps, regardless of whether is installed in However, if the project does not use vue, these dependencies are simply not used, in other words they are optional and are only needed for a certain tech stack What's wrong with unnecessary dependencies that will never be used in some projects? I would say it's not a critical problem, but such dependencies cause some inconvenience:
Thus, making these dependencies optional not only better reflects reality, but will make the users of this wonderful library a little happier ; ) |
I'd add to some downsides, these Vue dependencies that my project doesn't use caused dependency resolution conflicts because they specify a different version of |
Describe the bug
In case it used in pure node.js app or for example in react app - it unnecessary adds such dependencies as
@vue/language-core
,@vue/compiler-core
,@vue/compiler-dom
, batch of@volar/**
packages and so on.Can be fixed by moving next packages to peerDependencies or optionalDependencies
Reproduction
not related
Steps to reproduce
pnpm add vite-plugin-dts
System Info
Validations
The text was updated successfully, but these errors were encountered: