You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the problem/challenge you have
The graphql-registry uses the listen function to start the server what forces the user to deploy as a docker container or a traditional server. With that way, it's not possible to extends the graphql-registry with plugins, custom logic, or use in a serverless environment (which is my case) .
Describe the solution you'd like
Publish this repository as a npm package too.
The graphql-registry could be exported as a fastify middleware. With that, will be possible to extends the logic and use in another kind of environment like aws lambda, google cloud functions, azure functions or other else. Let the user decide the deployment type.
Anything else you would like to add:
I'm available to make a pull request for this feature, I will only need help to publish the package.
Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.
The text was updated successfully, but these errors were encountered:
Hello guys.
Describe the problem/challenge you have
The graphql-registry uses the
listen
function to start the server what forces the user to deploy as a docker container or a traditional server. With that way, it's not possible to extends the graphql-registry with plugins, custom logic, or use in a serverless environment (which is my case) .Describe the solution you'd like
Publish this repository as a npm package too.
The graphql-registry could be exported as a fastify middleware. With that, will be possible to extends the logic and use in another kind of environment like aws lambda, google cloud functions, azure functions or other else. Let the user decide the deployment type.
Anything else you would like to add:
I'm available to make a pull request for this feature, I will only need help to publish the package.
Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.
The text was updated successfully, but these errors were encountered: