⬆️v5 -> v6
Migration guide from v5 to v6
Main script renamed to keycloakify
keycloakify
You can search and replace build-keycloak-theme
-> keycloakify
in your project.
package.json
.github/workflows/ci.yaml
Components exported using default export
In order to enable you to use React.lazy()
, Keyclaokify components are now exported with default exports instead of named exports.
Once you're at it, it might be a good time to update your app to use <Suspense/>
and React.lazy()
in order to reduce your bundle size. See keycloakify-starter (CSS only) or keycloakify-advanced-starter (component level customization) to see how it's suposed to be setup.
You can also have a look at a real world migration:
i18n: Adding i18n messages keys
In v5 and prior, Keycloakify only provided a very hacky way of customizing internatiznalized message.
Keycloakify v6 now has a proper i18n api.
🌎i18n: msg(...)Tems and conditions
The message termsTitle
(Terms and Conditions in en.ts) was repmaced by a blank string in v5. If you want to do the same in v6 you have to use the new i18n API.
If you have perfomed an modification at the component level of the Terms.tsx component be mindfull that we now use an Evt to re render when the terms Markdown have been downloaded.
useFormValidationSlice()
useFormValidationSlice()
now require you to pass a i18n object, see I18n API.