Skip to content
This repository has been archived by the owner on Apr 17, 2023. It is now read-only.

Not working with graphql@^16.0.0 #137

Open
buenaondalab opened this issue May 21, 2022 · 8 comments
Open

Not working with graphql@^16.0.0 #137

buenaondalab opened this issue May 21, 2022 · 8 comments

Comments

@buenaondalab
Copy link

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

@wtrocki
Copy link
Contributor

wtrocki commented May 21, 2022

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

@buenaondalab
Copy link
Author

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

@dbateman
Copy link

dbateman commented Jun 7, 2022

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?

@wtrocki
Copy link
Contributor

wtrocki commented Jun 7, 2022

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

@dbateman
Copy link

dbateman commented Sep 21, 2022

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

@Kars-de-Jong
Copy link

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.

@dbateman
Copy link

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

@wtrocki
Copy link
Contributor

wtrocki commented Mar 20, 2023

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants