-
Notifications
You must be signed in to change notification settings - Fork 575
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API requests fail with: Invalid options provided to ApolloServer #34
Comments
Thanks for reporting this @nikolasburk. @kbrandwijk could you have a look into this as this seems to be related to your recent PR. |
|
The issue still seems to persist. You should be able to reproduce the problem here: https://github.com/graphql-boilerplates/node-graphql-server/tree/master/basic |
Fixed after all dependencies across all packages were updated to the same graphql version (0.12). |
awesome! |
Hey, @Urigo from The Guild here! You might know us from projects such as graphql-code-generator, envelop or graphql-tools. For a long time we thought that the Javascript ecosystem is still missing a lightweight cross-platform, but still highly customizable GraphQL Server. In the past the awesome Prisma team took on that great challenge and now we are happy to announce that we are continuing them and just released GraphQL Yoga 2.0 - Build fast, extensible, and batteries-included (Subscriptions, Serverless, File uploads support) GraphQL APIs in Node.js 🚀 We have been working a long time on version 2.0 and have been using it in our clients projects for a few months now and shared a couple of alpha cycles here. Please try Yoga out again, give us feedback and help us spread the word on the new release! |
The last release seems to be broken. I was creating and starting my yoga server as follows:
However, I was not able to access the API on
http://localhost:4000
, the Playground could not load the schema but failed with an internal server error and the message:Invalid options provided to ApolloServer:
.Rolling back to version
0.3.0
fixed the problem.The text was updated successfully, but these errors were encountered: