GraphQL config is not loaded from package.json in graphql-language-service-server
See original GitHub issueGraphQL configuration is loaded from .graphqlrc
files, graphql.config.js
files and other .rc
or .config
files, but not from the graphql
key in package.json
.
This is an upstream issue with the graphql-config
module, which is overriding the default cosmiconfig
search paths, and it’s being tracked here:
https://github.com/kamilkisiela/graphql-config/issues/692
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:7 (5 by maintainers)
Top Results From Across the Web
GraphQL config is not loaded from package.json #2020 - GitHub
Actual Behavior GraphQL config is not loaded from package.json. This is actually an upstream issue caused by the graphql-config package ...
Read more >graphql-language-service-server - npm
Start using graphql-language-service-server in your project by running `npm i ... .graphqlrc or .graphqlrc.json or graphql.config.json.
Read more >Nvim-lspconfig: Can't get graphql LSP working - Plugins
I'm following the GraphQL Apollo Tutorial here, so my project is very simple. The schema file is in src/schema.gql . So the graphql.config.js...
Read more >Usage – GraphQL Config
graphql property in package.json. Schema. The simplest config specifies only schema which points to the source of GraphQL Schema. schema: .
Read more >Graphql-config NPM
Check Graphql-config 4.3.5 package - Last release 4.3.5 with MIT licence at ... to maintain the code responsible for handling configuration, loading GraphQL...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi! Sorry, I meant to also create a pull request here to bump
graphql-config
to 3.3.0, after my pull request with the fix was merged, but I didn’t want to involve my employer in the whole CLA signing process just for that and I didn’t get the chance to do it in my spare time either… IMHO, just a version bump would be the easiest way to fix this without causing too much trouble downstream, to other projects.There was a release last night that should fix this issue in both the language server here and
vscode-graphql
- we just needed to add anactivationEvent
of*
because vscode extensions have no way of checking package.json to decide to activate.