Stopped working after upgrade
See original GitHub issueI was using this library for a long time with no problems. I used to call this command
gql-gen --url http://endpoint/graphql/ --template typescript --out ./assets/js/Typings/GraphQL.d.ts
when --url
option existed.
Now after upgrade I call similar command but receive unspecified error
$ DEBUG=true gql-gen --schema http://endpoint/graphql/ --template typescript --out ./assets/js/Typings/GraphQL.d.ts
11:03:33.034 - info: [executeWithOptions] using template: typescript
11:03:33.038 - error:
error Command failed with exit code 1.
What might be wrong? Is it because I use graphql 14.0.0?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
server manager has stopped working after upgrade from 2008 ...
Hi,. I have a problem after upgrade from 2008 r2 to 2012 r2, the server manager has stopped working and the updates the...
Read more >Windows 11 Not Working After Update? 12 Fixes - groovyPost
1. Restart Your PC · 2. Uninstall the Update · 3. Pause Updates · 4. Reinstall the Update · 5. Run the Windows...
Read more >Windows Update Not Working for Your Latest Upgrade ...
Windows Update not working for your latest upgrade? Here's how to fix it · Manage automatic updates · Windows 10 Update Change Active...
Read more >K48097216: Cloud failover stopped working after upgrade
K48097216: Cloud failover stopped working after upgrade · From the Configuration Utility, Navigate to 'iApps > Package Management LX' · Select the ...
Read more >Terminal stopped working after upgrading to Ubuntu 22.04
after upgrading my terminal stopped working. Terminal is installed and I can see it in my favourites also in the application section, but...
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
@simPod this issue with the location is because of GraphQL 14, it was fixed and I’ll release a version with a fix for it very soon 😃
@kamilkisiela yes it seems that it’s the same, thanks!
Now I’m getting different error, something about Introspection result missing directive locations but I guess I’ll solve it when there’s a message now 😃
Best!