graphql / graphql/graphiql

Code Navigation issue when using PNPM workspaces

Open
#2,344 2 comments 0 reactions 0 assignees View on GitHub
lsp-server
Dominant language
TypeScript
Stars
16.9k
Forks
1.9k
Avg merge
22h 45m
Merged PRs (30d)
70

Description

## Actual Behavior

Hi. I have my project setup as a [PNPM workspace](https://pnpm.js.org/en/workspaces) and VSCode GraphQL has been working well except for 1 issue - It navigates within `node_modules` folder where PNPM has symlinked the file (as part of PNPM workspaces) instead of the actual file itself. I am adding a gif below demonstrating the same:

![vscode-nav-bug](https://user-images.githubusercontent.com/1165845/101070013-c9c42500-35c0-11eb-8df7-e32a88fd9451.gif)

If you notice, the real fragment file is within `sdk/fragments` but it gooes inside `node_modules` and gets the same file from the symlinked `node_modules` folder.

## Expected Behavior

Code navigation navigates to the real graphql file instead.

## Specifications

- GraphQL for VSCode Extension Version: v0.3.13
- VSCode Version:

```
Version: 1.52.0-insider (user setup)
Commit: f4187f22026ff6537f2ca8132ad3209fceb5071f
Date: 2020-12-02T13:21:33.226Z
Electron: 9.3.5
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.20201
```

- OS: Ubuntu server 20.04

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.