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
{{ message }}
This repository has been archived by the owner on Sep 20, 2022. It is now read-only.
The dependency resolution in Apollo Launchpad is kind of non-deterministic. I just logged into the launchpad and it worked, then saved and it did not work again.
It seems as this is a bug in Apollo Launchpad. The graphql package is installed twice (once in the root, and once at launchpad-module/node_modules), although both point to the same version. The root cause could be that launchpad-module declares a regular dependency to graphql instead of a peerDependency, and sometimes the other packages (graphql-weaver, graphql-tools) are installed too late so that graphql is already installed within launchpad-module and gets installed a second time in the root package. I don't know why this is not a problem with graphql-tools on its own.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Can you please refresh the graphql endpoint examples and namespacing examples on launchpad?
The text was updated successfully, but these errors were encountered: