Skip to content
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

VS Code issue tracker #6569

Open
fulldecent opened this issue Oct 21, 2024 · 6 comments
Open

VS Code issue tracker #6569

fulldecent opened this issue Oct 21, 2024 · 6 comments
Labels
waiting for feedback Will autoclose in a while unless more data are provided

Comments

@fulldecent
Copy link
Contributor

fulldecent commented Oct 21, 2024

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
Copy link
Member

arcanis commented Oct 21, 2024

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.

@arcanis arcanis added the waiting for feedback Will autoclose in a while unless more data are provided label Oct 21, 2024
@fulldecent
Copy link
Contributor Author

fulldecent commented Oct 21, 2024

Thank you for these two references, I added my thumbs up on those linked issues!

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!

@yarnbot
Copy link
Collaborator

yarnbot commented Dec 15, 2024

Hi! 👋

It seems like this issue as been marked as probably resolved, or missing important information blocking its progression. As a result, it'll be closed in a few days unless a maintainer explicitly vouches for it.

@yarnbot yarnbot added the stale Issues that didn't get attention label Dec 15, 2024
@fulldecent
Copy link
Contributor Author

Created PR here #6600

This will help us bring attention and fix the upstream VS Code issue.

@yarnbot yarnbot removed the stale Issues that didn't get attention label Dec 16, 2024
@Stanzilla
Copy link

Is the issue only with pnp enabled or are the general issues with berry + vscode?

@fulldecent
Copy link
Contributor Author

I'm not sure how this works, but I think if Yarn Berry is using node modules then there's no problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting for feedback Will autoclose in a while unless more data are provided
Projects
None yet
Development

No branches or pull requests

4 participants