Apollo-server: Two versions of graphql-extensions used (0.8.1/0.9.1) by apollo-server-core 2.8.1

[bxt]

Expected behavior

The latest apollo server packages are compatible with the latest version of graphql-extensions.

The actual behavior

Packages [email protected] and [email protected] are dependent on outdated [email protected].

Reproduction

mkdir tmp && cd tmp
npm i graphql
npm i apollo-server-core
npm list graphql-extensions

It will give an output like this:

`-- [email protected]
  +-- [email protected]
  | `-- [email protected]  extraneous
  +-- [email protected]
  | `-- [email protected]  deduped
  +-- [email protected]
  | `-- [email protected]  extraneous
  `-- [email protected] 

Notice the "extraneous" entries.

It is a little bit strange to reproduce, since in the repo all packages have file: dependencies. It seems to be a problem in the release tooling. As far as I can tell, there were no recent changes to graphql-extensions that would even justify a new version.

The last version of Apollo where the problem did _not_ occur.

It worked with 2.7.1:

`-- [email protected]
  +-- [email protected]
  | `-- [email protected]  deduped
  +-- [email protected]
  | `-- [email protected]  deduped
  +-- [email protected]
  | `-- [email protected]  deduped
  `-- [email protected] 

And stopped working with 2.7.2.

[kachkaev]

Same problem after deleting yarn.lock, running yarn install and starting the dev server. Playground loads, none of the queries work.

Seems to be caused by apollo-server-express 2.7.0 → 2.8.1 with all its dependencies (and thus resulting multiple versions of graphql-extensions). I had to undo within-range changes in yarn.lock till this issue is resolved.

[abernix]

Could you try this again with 2.9.1?

[abernix]

Thanks to your reproduction, I can confirm this is fixed by Fixed by 8b21f83286c68fa9a8f63c781244ee511d9a52f5 and f710fe46c90ce22ccc6611050ec21c42e0d833d4 in the latest version of Apollo Server:

$ npm ls graphql-extensions
[email protected] /private/var/folders/mq/s5hmqjmx7djftqd_2fqjfn0w0000gn/T/tmp.u0122yJE
└─┬ [email protected]
  ├─┬ [email protected]
  │ └── [email protected]  deduped
  ├─┬ [email protected]
  │ └── [email protected]  deduped
  ├─┬ [email protected]
  │ └── [email protected]  deduped
  └── [email protected]

Thanks for reporting this originally!

[bxt]

@abernix Yes, it works 🎉 thank you so much for fixing this 🙏