VS Code issue tracker

[fulldecent]

Using Yarn Berry with VS Code, especially with TypeScript is is like omgwtfbbq

If ChatGPT didn't exist, you would give up on making it work. Be honest.

---

May the Berry project please have a vision of how VS Code should improve to work with Berry, and include a link to related issues on the VS Code repo?

You could include those in our README here, saying like:

Using with VS Code

We imagine a future where using VS Code with your Yarn Berry projects will work seamlessly. Here are specific projects we hope will be addressed:

• vscode issue 1
• vscode issue 2
• ...

This could be powerful in helping coalesce around a specific plan for VS Code, and for concentrating our support.

PS The VS Code directly counts the number of 👍 on issue when deciding which to prioritize. So if we do that here then we can farm the number of required 👍 to fix VS Code.

[arcanis]

Well it's not complicated: natively support zip files in VSCode (ie microsoft/vscode#75559), and native TS support for PnP (ie microsoft/TypeScript#35206). Both of those are already popular, but the friction to implement them makes them unlikely to be implemented unless Microsoft benefits directly enough from them that they'd be willing to accept the potential maintenance cost that would come with them.

For everything else we already have a VSCode documentation.

[fulldecent]

Thank you for these two references, I added my thumbs up!

I hope your two references can be added to the readme file. Probably 80% of people using Yarn Berry also use VS Code and experience this suboptimality. Documenting this acknowledges that we still have opportunity to improve.

---

For me personally, Yarn Berry + TypeScript + Prettier + plug-ins sounds great but does not justify the complexity.

So I'm going back to the plebe stack. Your vision for 10x better developer DX is epic and keep it up, we all want that future!