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

[Bug?]: vscode go to definition not working #4182

Closed
Jungho-Cheon opened this issue Mar 4, 2022 · 3 comments
Closed

[Bug?]: vscode go to definition not working #4182

Jungho-Cheon opened this issue Mar 4, 2022 · 3 comments
Labels
bug Something isn't working stale Issues that didn't get attention

Comments

@Jungho-Cheon
Copy link

Jungho-Cheon commented Mar 4, 2022

Describe the bug

The zipfs extension doesn't seem to work since vscode was automatically updated. Errors occur when accessing files for all external dependencies. The vscode error message is:

Unable to open 'index.d.ts': Unable to resolve resource zip:/...

Is this a vscode version issue? I downgraded to version 1.60.2, but the same problem occurred.

Environment

System:
  OS: macOS 11.5.1
  CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
Binaries:
  Node: 14.19.0 - /private/var/folders/gw/_bxxmpwj5xzbrswm33pgqtpc0000gp/T/xfs-53196e67/node
  Yarn: 3.1.1 - /private/var/folders/gw/_bxxmpwj5xzbrswm33pgqtpc0000gp/T/xfs-53196e67/yarn
  npm: 6.14.16 - /usr/local/bin/npm

Additional context

vscode version: 1.65.0
zipfs extension installed
run yarn dlx @yarnpkg/sdks vscode
set the typescript version to .yarn/sdk/typescript

@Jungho-Cheon Jungho-Cheon added the bug Something isn't working label Mar 4, 2022
@bradennapier
Copy link

Also having this issue now

@mrmartineau
Copy link

I experienced this issue and the only thing that worked was to revert the TypeScript version to v4.4.4. See this issue for more info: #3722

@yarnbot
Copy link
Collaborator

yarnbot commented Apr 28, 2022

Hi! 👋

This issue looks stale, and doesn't feature the reproducible label - which implies that you didn't provide a working reproduction using Sherlock. As a result, it'll be closed in a few days unless a maintainer explicitly vouches for it or you edit your first post to include a formal reproduction (you can use the playground for that).

Note that we require Sherlock reproductions for long-lived issues (rather than standalone git repositories or similar) because we're a small team. Sherlock gives us the ability to check which bugs are still affecting the master branch at any given point, and decreases the amount of code we need to run on our own machines (thus leading to faster bug resolutions). It helps us help you! 😃

If you absolutely cannot reproduce a bug on Sherlock (for example because it's a Windows-only issue), a maintainer will have to manually add the upholded label. Thanks for helping us triaging our repository! 🌟

@yarnbot yarnbot added the stale Issues that didn't get attention label Apr 28, 2022
@yarnbot yarnbot closed this as completed May 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale Issues that didn't get attention
Projects
None yet
Development

No branches or pull requests

4 participants