chore: migrate from express-graphql to graphql-http #37001
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gatsbot
bot
added
the
status: triage needed
pieh
added
type: maintenance
LekoArts
approved these changes
Nov 9, 2022
This was referenced Nov 22, 2022
Open
Open
Open
This was referenced Nov 22, 2022
Open
Open
Open
This was referenced Nov 22, 2022
Open
Open
This was referenced Nov 23, 2022
Open
Open
This was referenced Nov 23, 2022
Open
Open
Open
Open
Open
Open
This was referenced Nov 23, 2022
Open
Open
Open
This was referenced Apr 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
See graphql/express-graphql#816 +
express-graphqldoesn't have updated peer deps for graphql@16, causing quite a lot of problems when installing with npm (for whatever reason yarn seems to more resilient to things like that). This is attempt at 1:1 replacement preserving some customizations we had weithexpress-graphql( showing stack traces per graphql error + showing some toggles as extensions)Related Issues
[ch-58093]