Jon Koops
Jon Koops
Investigation is still needed to determine whether the change can be made in a non-breaking way. I would advise to test this theory against a complex dependency such as `@patternfly/react-core`...
@tlabaj can this issue be pinned?
@kmcfaul perhaps it can be done without breaking things, but it would mean exporting everything in the package and then in the next major removing most of the exported API...
Could this issue be pinned?
This one can be closed now that #75 was merged.
Like already mentioned no dates have been set.
We have not yet set a date for full deprecation and removal. We will continue to land CVE fixes, but will no longer be accepting new features.
@mircicd I think the best place to look for that is in [the discussion](https://github.com/keycloak/keycloak/discussions/9818) around this topic.
@rolandjitsu Deno only [recently introduced](https://deno.com/blog/v2.0) backwards compatibility with Node.js and NPM, so at the time this issue was logged it did not work. I think this can safely be closed...
I suspect part of the error message might be obscured due to #30705. If you check the network request in the browser you might get a more detailed error message.