Jon Koops
Jon Koops
Yes, this issue will likely be closed with the release of version 2.0. We're all running this on volunteer work, so we cannot really give an eta of when this...
This bug should be re-opened and fixed, it is an issue in Yarn v1, since it is still the default, even when initializing a new project. This is actively causing...
I can confirm this also fixes issues with module resolution when using TS Node and ESM.
This dependency upgrade requires some migration, let me know if assistance is needed, I've already upgraded a couple of projects using Husky.
The discussion as to what the alternative would be is not related to this issue, and is already being discussed under https://github.com/keycloak/keycloak/discussions/9818, hence these comments are off topic.
The latest releases after 1.12.1 are also missing.
> How come this being classified as an enhancement if in the API docs it has an id field on the request payload? It should either be supported or have...
I am re-opening this issue as it is highly upvoted and the issue it was closed in favour of (#14134) is only applicable for importing, not the REST API.
Note, when fixing this issue I think it is important this done as a generic solution for all things that are indexed with an `id`, not just the users.
This issue has been resolved by upgrading the `js-sha256` dependency to the latest version, which removes the use of `eval()`.