tobias frei

You have to extend the tsconfig with baseUrl and path. https://github.com/tobiasfrei/react-keycloak-fork/blob/master/packages/ssr/tsconfig.json#L26

If you look at the issue tracker, I would say yes. For keycloak support >=17 a fork is available, the adjustments for this were trivial and would be done quickly....

it affects also 'keycloak v18.0.0', change needed in node_modules/@react-keycloak/ssr/lib/internals/keycloak.js Line 20 (import default): `var Keycloak = !isServer() ? require('keycloak-js').default : null;` Line 25 (remove constructor): `keycloakInstance = Keycloak(keycloakConfig);` You are...

I've forked an updated package with Keycloak >=17 support until this one is back, you can use `npm i @react-keycloak-fork/web --save` and `npm i @react-keycloak-fork/ssr --save` [@react-keycloak-fork/web](https://www.npmjs.com/package/@react-keycloak-fork/web) [@react-keycloak-fork/ssr](https://www.npmjs.com/package/@react-keycloak-fork/ssr)

> I've forked an updated package with Keycloak >=17 support until this one is back, you can use `npm i @react-keycloak-fork/web --save` and `npm i @react-keycloak-fork/ssr --save` > > [@react-keycloak-fork/web](https://www.npmjs.com/package/@react-keycloak-fork/web)...

> Please don't delete the package, I have a project using it due in 3 days and don't have the time to upgrade. (It's only a "testing"-project with no real...