Carbon Web Components V2: Full Release

Ariella Gilmore
_carbondesign
Published in
2 min readAug 17, 2023

Following up: Release Candidate: Carbon Web Components v2, Introducing: Carbon Web Components v2, & Coming soon: Carbon Web Components v2

The Carbon Design System team is excited to announce the full release 2.0.0 of Carbon Web Components!

These are the main highlights in v2.0.0:

  • Upgrade to Carbon Design System v11
  • Upgrade to Lit v2
  • Upgrade to Typescript v4
  • Existing component baseline sync with Carbon React

Since the first release candidate, we have rigorously tested and received feedback from our users so that we can create the best 2.0.0 experience we can. Thank you to everyone that tested the release candidates and supported us during this period!

Migration documentation

When migrating from @carbon/web-components v1 to v2, our team has created a migration guide which features a table outlining changes for each component.

Each component on Storybook has a “docs” tab that describes how to use the component with optional JS implementations either via import or CDN. There also is a CodesandBox link to show the component working in isolation outside of the Storybook environment.

Just as we have v10 CDN helpers for theming and grid, we also released v11 CDN helpers for theming and grid. Checkout the Carbon CDN style helper page or the migration guide for how to set up theming for your application.

Websites

Since v1 will still be in maintenance mode, there will be both a v1 and v2 Storybook website available here: v1 and v2. The Carbon Design system website also has separate versions of Web components information here: v10 and v11.

Any questions?

Looking for support or have a bug/feature request related to @carbon/web-components? Our team actively monitors any new issues that are added to our github repository. For IBMers, it’s best to use the #carbon-web-components Slack channel.

What’s next?

Our team will continue to stay closely aligned to @carbon/react. Also, there will be a focus to improve the end-to-end and unit tests, so as component updates are made, the tests will ensure there are no bugs for the adopters.

--

--