-
Notifications
You must be signed in to change notification settings - Fork 48
create separate package for @graphql-helix/core #140
base: main
Are you sure you want to change the base?
Conversation
@n1ru4l is there anything I can do to move this forward? |
@mosch, I did not have a look yet, but will on Thursday. Can you rebase upon master until then? |
# Conflicts: # packages/core/package.json
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/graphql-helix/graphql-helix/DUwDk1qFoZ7hKWmQNRTdXUCwiW1s |
@@ -1,5 +1,5 @@ | |||
import express, { RequestHandler } from "express"; | |||
import { getGraphQLParameters, processRequest, renderGraphiQL, sendResult, shouldRenderGraphiQL } from "../../lib"; | |||
import { getGraphQLParameters, processRequest, renderGraphiQL, sendResult, shouldRenderGraphiQL } from "../../../graphql-helix"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should move this folder (test/implementations
) to packages/graphql-helix
.
@@ -1,8 +1,2 @@ | |||
export * from "./get-graphql-parameters.ts"; | |||
export * from "./process-request.ts"; | |||
export * from "@graphql-helix/core DENOIFY: DEPENDENCY UNMET (BUILTIN)"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This warning seems dangerous? DENOIFY: DEPENDENCY UNMET (BUILTIN)
I am actually not really aware of all the deno shenanigans, it might be worth adding a deno integration test suite in a separate PR first, so we can verify this PR does not break the behavior?
@mosch Shouldn't the be also a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added some comments
Since @mosch probably will be out for a while, I might as well take this over. Thanks ✌️ edit: (don't know why vercel tests fail) |
Deployment failed with the following error:
|
Hey @dan-lee, sorry for letting this slip so long. Do you mind rebasing and finishing this PR? Let's finish this and release it. |
is this PR still relevant? seems like it went nowhere since 2022 |
asfaik it's not really maintained and would recommend for you to use GraphQL Yoga. Explain it more in the doc here https://the-guild.dev/graphql/yoga-server/docs/comparison#graphql-yoga-and-graphql-helix |
Hey there,
we have done our best to solve the package size issue.
This may not be complete, especially around the deno packages.
Looking for some early feedback on this one 🤞🏻 @n1ru4l @talentlessguy @danielrearden