Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Cannot read property 'definitions' of undefined.
See original GitHub issueHi, in this new release (v0.6.2), the CLI fails with below error.
I tried cleaning up the workspace (rm -rf node_modules yarn.lock generated .next) and also to revert back to v0.5.2. I’m not sure about this error but I suspect it might be from @graphql-codegen/typescript-operations but it’s just an assumption.
Issue Analytics
- State:
- Created 4 years ago
- Comments:14 (8 by maintainers)
Top Results From Across the Web
Minimal example throws "Cannot read property 'definitions' of ...
I'm trying to create a minimal GraphQL server example using Apollo Server. However, when I make a request to it, it responds with...
Read more >Error when building typedefs TypeError: Cannot read property ...
I am getting the following error when building Typedefs in Apollo Server: return typeDef.definitions.some( ...
Read more >Uncaught TypeError: Cannot read property of undefined In
Uncaught TypeError : Cannot read property of undefined error occurs in Chrome when you read a property or call a method on an...
Read more >How to Prevent the Error: Cannot Read Property '0' of Undefined
A guide on how to prevent the error "cannot Read Property '0' of Undefined", covering techniques such as try, catch, using const over...
Read more >Cannot read property 'launchAPI' of undefined in Apollo ...
Hi, there. I'm trying the following query in Apollo Graphql Studio while checking the tutorial. query GetLaunches { launches { id mission {...
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 Free
Top 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
@ALITHEALI @Rudy-Clark The new v0.6.2 should work, sorry for bothering you. I’ll investigate the root cause and why the CI wasn’t failed despite the yarn.lock.
It’s in
node_modules/@graphql-toolkit/common/index.cjs.js. Possibly one of the plugins changes its behavior as you said. I’ll check it.