Hello I am trying to move from cjs to esm I am using Apollo graphql and this error is bringing on lambda invokes:

Unhandled Promise Rejection     {"errorType":"Runtime.UnhandledPromiseRejection","errorMessage":"Error: Cannot use GraphQLNonNull \"Boolean!\" from another module or realm.\n\nEnsure that there is only one instance of \"graphql\" in the node_modules\ndirectory. If different versions of \"graphql\" are the dependencies of other\nrelied on modules, use \"resolutions\" to ensure only one version is installed.\n\n<https://yarnpkg.com/en/docs/selective-version-resolutions>\n\nDuplicate \"graphql\" modules cannot be used at the same time since different\nversions may have different capabilities and behavior. The data from one\nversion used in the function from another could produce confusing and\nspurious results.","reason":"Error: Cannot use GraphQLNonNull \"Boolean!\" from another module or realm.\n\nEnsure that there is only one instance of \"graphql\" in the node_modules\ndirectory. If different versions of \"graphql\" are the dependencies of other\nrelied on modules, use \"resolutions\" to ensure only one version is installed.\n\n<https://yarnpkg.com/en/docs/selective-version-resolutions>\n\nDuplicate \"graphql\" modules cannot be used at the same time since different\nversions may have different capabilities 
and behavior. The data from one\nversion used in the function from another could produce confusing and\nspurious results.","promise":{},"stack":["Runtime.UnhandledPromiseRejection: Error: Cannot use GraphQLNonNull \"Boolean!\" 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.

I tried to use yarn resolutions like this:

"resolutions": {
    "graphql": "15.5.1"
  }

But It didn't solve the problem. I have monorepo, and I tried to unify versions of many related dependencies between repos did anyone faced this?

Many. Publish Apollo Server packages in ESM · Issue #5627 · apollographql/apollo-server (github.com)

hmm I see, I am thinking if I exclude apollo dependencies from bundling and add it to the node_modules zip does that effect the performance ? @Derek Kershner

no idea, I moved to not using Apollo instead, and just using graphql-tools directly.

Yeah we abandoned Apollo once we discovered how unfriendly their setup is for ESM

Sounds a great option, but I don't know if moving from apollo federation to graphql-tools is a straight forward step or not,I will give it a try Thanks for your help @Derek Kershner @thdxr

It's very straightforward! Apollo is actually doing very little it's why we we're able to replace it without much effort

That's very good @thdxr

I am not using federation, so I am not sure how easy that would be, but frankly you could probably maintain apollo for federation and just run that app using

cjs

, and make the others graphql-tools and

esm

hmm you mean to keep the apollo gateway only, and other services move graphql-tools? @Derek Kershner

that exactly

oh I did miss the word federation 😅