-
Notifications
You must be signed in to change notification settings - Fork 65
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
1.0 Release #126
Comments
How to use it with GrahQL If I use it in my production build, how difficult could it be to switch to expressjs later? |
You can always switch to express by replace |
What about using GraphQL with next-connect? And even if I achieve it will it work on Vercel serverless? |
It definitely works: // api/graphql.js
const nc = require("next-connect");
const { graphqlHTTP } = require("express-graphql");
module.exports = nc()
.use(middleware)
.all(graphqlHTTP({
schema: MyGraphQLSchema
})); |
Would it be smart to include support for the new middleware support in Next.js? Or do you see that as a v2? Or never ;-) |
It is totally possible. I am just wondering what would be a good naming for this functionality:
|
I think I would go with the second one. |
This library has been sitting in v0 for awhile. After a period of using it in several production apps, it does not seem to yield any problems. After all, most crux of this library depends on the awesome https://github.com/lukeed/trouter library, so nothing much can really go wrong.
Before the 1.0 release though:
http
very fine. Therefore, it should be about more than Next.js.The text was updated successfully, but these errors were encountered: