-
Notifications
You must be signed in to change notification settings - Fork 2k
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
apollo-server-core has a hardcoded dependency on graphql 14.7.0 #4413
Comments
should be upgraded to graphql-upload 11.0.0 to fix this. Ah shit. @types/graphql-upload is outdated |
Yup. Looks like the version of CC: @abernix |
Any update on this ? |
any update of this? |
any update?? This is a serious issue |
Any update on this? I saw there was new release but it still not resolve |
Apollo server core depends on 14.7.0, whereas apollo-server-express has a peerdependency permitting 15.0.0.
This can create problems in monorepos and is for me. I can prob work around it, but the @types/graphql-upload is already a year old. It should prob be updated to 8.0.3
Versions
apollo-server-express: 16.0
Expected
depend on graphql 15 and allow resolving to that version
Actual
Resolving to graphql 15.x results in a build error with
yarn install --frozen-lockfile
This bug report should include:
[x ] A short, but descriptive title. The title doesn't need "Apollo" in it.
[ x] The package name and version of Apollo showing the problem.
If applicable, the last version of Apollo where the problem did not occur.
[ x] The expected behavior.
[ x] The actual behavior.
A simple, runnable reproduction!
Please make a GitHub repository that anyone can clone and run and see the
problem. Other great ways to demonstrate a reproduction are using our
CodeSandbox template (https://codesandbox.io/s/apollo-server), or re-mixing
our Glitch template (https://glitch.com/~apollo-launchpad).
Please make sure that you include the following information to ensure that your issue is actionable.
If you don't follow the template, your issue may end up being closed without anyone looking at it carefully, because it is not actionable for us without the information in this template.
-->
The text was updated successfully, but these errors were encountered: