Releases: cultureamp/kaizen-design-system
@kaizen/[email protected]
Patch Changes
-
#5391
d180512
- Deps updates and type component fixes for RC MenuItem and Tab- Update deps
- Update RC MenuItem and Tab child render to fix types issues after upgrade to typescript 5.7.3 upgrade
- Update test-runner to use imported Page type from Playwright to reflect updated dep
- Update Badge duplicate color declaration
-
Updated dependencies [
d180512
]:- @kaizen/[email protected]
@kaizen/[email protected]
Patch Changes
-
#5391
d180512
- Deps updates and type component fixes for RC MenuItem and Tab- Update deps
- Update RC MenuItem and Tab child render to fix types issues after upgrade to typescript 5.7.3 upgrade
- Update test-runner to use imported Page type from Playwright to reflect updated dep
- Update Badge duplicate color declaration
@kaizen/[email protected]
Patch Changes
-
#5391
d180512
- Deps updates and type component fixes for RC MenuItem and Tab- Update deps
- Update RC MenuItem and Tab child render to fix types issues after upgrade to typescript 5.7.3 upgrade
- Update test-runner to use imported Page type from Playwright to reflect updated dep
- Update Badge duplicate color declaration
@kaizen/[email protected]
Patch Changes
-
#5391
d180512
- Deps updates and type component fixes for RC MenuItem and Tab- Update deps
- Update RC MenuItem and Tab child render to fix types issues after upgrade to typescript 5.7.3 upgrade
- Update test-runner to use imported Page type from Playwright to reflect updated dep
- Update Badge duplicate color declaration
@kaizen/[email protected]
@kaizen/[email protected]
@kaizen/[email protected]
@kaizen/[email protected]
@kaizen/[email protected]
Patch Changes
-
#5426
7303979
- Support having multiple KaizenProvider on the same page.This is helpful when publishing a package which relies toast notification - setting up its own KaizenProvider (which also set up ToastNofitification) will ensure that we won't run into
useToastNotificationContext must be used within the ToastNotificationContext.Provider
as this relies on the consumers' applications having the exact@kaizen/components
version and depends on how package manager resolves peer deps. Especially for pnpm, it might end up with 2 copies of the exact same version of kaizen/components therefore won't be able to find theToastNotificationContext.Provider
set up by the application.