-
-
Notifications
You must be signed in to change notification settings - Fork 122
Graphql lsp does not currently support graphql@16 #221
Comments
Yes you can specify the version that you want, e.g. |
When specifying a version, it will only be applied to the "head" package, so if a server installs more than one npm package you're currently only able to specify the version for the first one 🙃
I'm not sure how to best deal with this particular issue. I was thinking perhaps adding a As for the GraphQL LSP, I think we could pin it to |
It seems to be installing graphql@15 though, I wonder if it's because of the peerDependency which specifies |
It's probably my node version not installing the correct pair dependency. To work around it I just cd'd to the install directory and installed graphql@15. I'm getting the same error as the guy in the linked issue but in the lsp logs |
I think the GraphQL LSP tries to use a project local |
@NICHTJ3 Is this still causing problems? I can't seem to repro - it's installing |
@williamboman So I decided to test this again today. The project version of graphql is 15.5.1 so that's definitely not the issue but reinstalling the lsp doesn't install version 16 like it did the otherday. I put it down to maybe running I'm going to close this issue since it's unrelated to this plugin 🤦♂️ |
This is an issue because the lsp installer for the graphql lsp installs the latest version of graphql. Is there something I can do to work around this quickly or do I have to create a custom server?
For more info see here
The text was updated successfully, but these errors were encountered: