Peer dependencies seems to break schema creation.

[jcblw]

I keep getting this issue not sure if its because of the setup in another extension of a issue with the library but it has been persistent and I have not been able to figure out the issue.

Uncaught Error: Cannot use GraphQLObjectType "Query" from another module or realm.

Ensure that there is only one instance of "graphql" in the node_modules
directory. If different versions of "graphql" are the dependencies of other
relied on modules, use "resolutions" to ensure only one version is installed.

https://yarnpkg.com/en/docs/selective-version-resolutions

Duplicate "graphql" modules cannot be used at the same time since different
versions may have different capabilities and behavior. The data from one
version used in the function from another could produce confusing and
spurious results.
    at instanceOf (instanceOf.js:29)
    at isObjectType (definition.js:138)
    at mapArguments (index.mjs:3156)
    at mapDefaultValues (index.mjs:3037)
    at Module.mapSchema (index.mjs:2953)
    at createNewSchemaWithResolvers (index.js:325)
    at addResolversToSchema (index.js:218)
    at addMiddlewareToSchema (middleware.mjs:11)
    at normalisedMiddlewares.reduceRight.schema.schema (middleware.mjs:40)
    at Array.reduceRight (<anonymous>)

I have already added resolutions to the package, and also confirmed that I only have one version of graphql installed.

[jcblw]

Actually ran into another one with the old version of Finch. Think this may be a break from a newer version of graphql or @graphql-tools/schema.

[jcblw]

This one actually is happening with adding multiple middlewares.

[jcblw]

Ok cleaned up dependencies in this project, and it's working again with the old version of Finch. So def one of the peer dependencies in this instance.

[jcblw]

Thinking this is potentially from a graphql-middleware update. I am seeing it trying to use a new version of the @graphql-tools/schema. Still attempting to verify this is the case.

[jcblw]

Ok seems like I have been able to get this working our solution, which may be too much is

  "resolutions": {
    "graphql": "^15.6.0",
    "@graphql-tools/schema": "7.1.5",
    "graphql-middleware": "6.0.4"
  }

The issue seems to stem from graphql-middleware 6.1.x having version 8 of @graphql-tools/schema. This was causing the issues.

[jcblw]

Thinking we should pin the correct middleware here, make the peers more specific to help others avoid this.

[jcblw]

This was a misconfiguration, not an issue with this library closing this issue.