-
-
Notifications
You must be signed in to change notification settings - Fork 489
Closed as not planned
Labels
questionFurther information is requestedFurther information is requested
Description
Vue - Official extension or vue-tsc version
3.0.4
VSCode version
1.102
Vue version
3.5.18
TypeScript version
5.8.3
System Info
System:
OS: Linux 6.12 Debian GNU/Linux 13 (trixie) 13 (trixie)
CPU: (8) x64 Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
Memory: 20.81 GB / 31.21 GB
Container: Yes
Shell: 4.0.2 - /usr/bin/fish
Binaries:
Node: 20.19.2 - /run/user/1000/fnm_multishells/44247_1753438232907/bin/node
Yarn: 4.9.2 - ~/.yarn/bin/yarn
npm: 10.8.2 - /run/user/1000/fnm_multishells/44247_1753438232907/bin/npm
bun: 1.2.8 - ~/.local/bin/bun
Browsers:
Chromium: 138.0.7204.157
package.json dependencies
Steps to reproduce
Use Yarn with PnP as your package manager in a project.
Upgrade Vue extension from 3.0.1 to 3.0.2.
See the breakage.
What is expected?
No breakage, or a clear documentation on what's missing.
The tooltip should explicitly mention "Yarn PnP" and a reference to #5505 to provide a solution for users with Yarn PnP.
What is actually happening?
Nothing, but feature are broken
Link to minimal reproduction
No response
Any additional comments?
I see that some people did raise the issue, like in #5520, but I'm not able to read this language, so I don't know if:
a. I'm concerned
b. There is a real solution provided
76fcd82 didn't really improve the situation, I tried so many times to restart Vue & TS server that I thought my machine was broken.
Metadata
Metadata
Assignees
Labels
questionFurther information is requestedFurther information is requested