Fix repository path for graphql-extensions

[kachkaev]

Avoids links with 404 on npm and yarn websites. Follows package migration to the monorepo.

---

It'd be great if someone also updated CHANGELOG.md before the next release 🙏 I’m currently seeing that I need to bump from ^0.10.10 to ^0.11.0 and I don’t know if there are any breaking changes to expect.

[abernix]

Thanks! (Also, thanks for helping me learn that using directory within repository was a thing!. I had no idea!)

Nothing has changed in graphql-extensions in some time, but it's a dependency of a number of things and internally the Lerna versioning scheme that we use necessitates bumping it unnecessarily sometimes, even when there aren't changes.

That said, we are planning on deprecating graphql-extensions in the next major version of Apollo Server so I would encourage you to explore the new Plugins API that will replace it and trying out that migration!

I hope to be implementing a couple of the missing bits of the new API this week, but aside from willResolveField and requestDidEnd, I don't believe there are any other omissions. In other words, depending on how you're leveraging graphql-extensions today, you'll be more or less successful at that migration. Please feel free to drop a comment here as to how it goes! (Please @ me!)

[abernix]

@kachkaev Fyi, #3988 has landed and brings graphql-extensions feature complete with the new plugin API. It's in the release-2.14.0 branch right now and published within #4105 (currently on the npm next tag).