Closed danLDev closed 3 months ago
FYI, vue-tsc
has been updated to fix this : https://github.com/vuejs/language-tools/issues/4610#issuecomment-2249800743
Please update vue-tsc to 2.0.29.
EDIT:
I can confirm using @vue/language-core@2.0.29
& vue-tsc@2.0.29
fix the issue :
"dependencies": {
"@microsoft/api-extractor": "7.47.2",
"@rollup/pluginutils": "^5.1.0",
"@volar/typescript": "^2.3.4",
"@vue/language-core": "2.0.29",
"debug": "^4.3.5",
"kolorist": "^1.8.0",
"magic-string": "^0.30.10",
"vue-tsc": "2.0.29"
},
Unfortunalty I'm not sure I can submit a PR as main branch is already on 4.x...
@qmhc Is this fix also going to be released to v3.. ? Ideally we'd like to resolve asap rather than wait for a major release as it's flagging up in our audit pipelines
@danLDev There are many breaking changes form Volar 1 to 2, so I thing we should update the major version when upgrading Volar.
The official v4 will be released in the next week.
Does upgrading to v4 of this package will require a lot of manual fixes?
If it's a simple version bump, it's probably fine (and should probably be a minor update version according to semver). However for bigger projects upgrading to v4 might not be an option if the upgrade process introduces breaking changes.
Such a simple fix (updating a dependency version) should be easily patched in a patch upgrade / security release for the current version. This is not possible by the current structure of this repo (no v3 branch available for PR submission).
Describe the bug
It seems this plugin is vulnerable to a vue vulnerability, we are using it to compile a react-lib, and not using vue anywhere.
https://github.com/advisories/GHSA-g3ch-rx76-35fx
Reproduction
https://github.com/advisories/GHSA-g3ch-rx76-35fx
Steps to reproduce
npm install npm audit
System Info
Validations