Carbon-themes has been deprecated in v10, as the carbon repository now contains the themes package @carbon/themes.
Carbon-icons has not yet been deprecated in favor of @carbon/icons. That is expected to happen in an upcoming dot release.
Carbon components have been completely re-skinned for the new IBM Design Language. The redesign was conducted with maximum backwards-compatibility in mind. Users of v9 should be able to upgrade to v10 automatically with minimal breakage.
Detailed technical migration docs for Carbon vanilla components are available in the carbon-components repo. Here you will find links to component-level migration information, as well as a list of those components that have been removed or are under development.
There is also a dedicated Sass migration guide that covers changes to global styling.
React-specific technical migration docs are available here.
All technical migration docs for Carbon Elements are available in the carbon repo’s docs folder.
Carbon icons underwent a major update for v10. The @carbon/icons package can be now be found in the Carbon Elements repo. This package will be publically available in an upcoming release, for now please continue to use the carbon-icons repo.
See the icons migration table to view .
The Carbon Icons Demo contains a master table for all Carbon icons, including name, size, preview, download links, quick links for filing issues, module name, and relative path.
The color token architecture for v10 is based on the v9 architecture, with some minor updates for the new design language. Carbon v9 users will see automatic, non-breaking color updates when they upgrade to v10.
The type token architecture has been completely redesigned for better clarity and flexibility in v10, moving from a basic type scale model to a more robust token-based architecture.
Spacing values will see no change from Carbon v9, though the token names have changed.
Motion standards have been revised to meet the new IBM Design Language standards. Motion updates should be coordinated with your product’s design team if possible.
To leave feedback for the Carbon team about this documentation, make suggestions for improvements, or just ask a question, you can open an issue on GitHub.