keycloak-connect-graphql icon indicating copy to clipboard operation
keycloak-connect-graphql copied to clipboard

Not working with graphql@^16.0.0

Open buenaondalab opened this issue 2 years ago • 8 comments

Could not resolve dependency: peer graphql@"^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0" from [email protected]

buenaondalab avatar May 21 '22 10:05 buenaondalab

You might use latest graphql. Package needs to be patched to support it.

wtrocki avatar May 21 '22 11:05 wtrocki

I installed the package with --force option. So far no issues.

buenaondalab avatar May 22 '22 07:05 buenaondalab

It seems to work fine with [email protected] but of course npm isn't happy about it. Can we get a bump to include the latest graphql as a peer please?

dbateman avatar Jun 07 '22 06:06 dbateman

I no longer actively use that library, but still maintain it. If you can test it with latest graphql-tools and graphql then we can update packages and examples

wtrocki avatar Jun 07 '22 09:06 wtrocki

What are you using as an alternative, if you are still using GraphQL and Keycloak together?

dbateman avatar Sep 21 '22 00:09 dbateman

Any progress on this? It work fine for us with GraphQL 16..6.0, but I must add that we only use the "Access to token/user information in resolver context via context.kauth (for regular resolvers and subscriptions)" functionality.

Kars-de-Jong avatar Jan 19 '23 12:01 Kars-de-Jong

If anyone is tired of using --force or --legacy-peer-deps, I've forked this repo and published a refactored version that works with graphql ^16.0.0 and graphql-tools ^9.0.0. It also has a convenient directive transformer function to use the @hasRole et al directives out of the box with Apollo Server 3/4 or compatible graphql server implementations. You can find it at https://www.npmjs.com/package/@dbateman/keycloak-connect-graphql

dbateman avatar Mar 20 '23 07:03 dbateman

@dbateman If you want to mantain package feel free to create PR updating readme to point to the fork

wtrocki avatar Mar 20 '23 09:03 wtrocki