-
Notifications
You must be signed in to change notification settings - Fork 59
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
Error with 'fs' and 'module' modules in front end #297
Comments
Thank you for reporting. In the last few months, since the transition of many libraries under The Guild's leadership, We've reviewed and released many improvements and versions to graphql-cli, graphql-config and graphql-import. We've reviewed What we've found is that the new GraphQL Mesh library is covering not only all the current capabilities of GraphQL Binding, but also the future ideas that were introduced in the original GraphQL Binding blog post and haven't come to life yet. And the best thing - GraphQL Mesh gives you all those capabilities, even if your source is not a GraphQL service at all! Just like GraphQL Binding, you get a fully typed SDK (thanks to the protocols SDKs and the GraphQL Code Generator), but from any source, and that SDK can run anywhere, as a connector or as a full blown gateway. If you think that we've missed anything from GraphQL Binding that is not supported in a better way in GraphQL Mesh, please let us know! In the context of that particular issue - GraphQL Mesh SDK can be used on the client, so you shouldn't have similar issues. We're looking forward for your feedback of how we can make your experience even better! |
When using graphql-binding in the front with Vuejs (through Nuxtjs) I end up having breaking errors regarding 'fs' and 'module' modules.
Won't you have a front-end version which would simplify the talking with the api?
Anyway, love the project. Just wanna find a way to make it work in the front-end if you've got any tips!
Error details:
Or am I wrong and I should never have tried it in the front end? :/
The text was updated successfully, but these errors were encountered: