Clarity Angular version 12 is available!
We’ve released Clarity Angular v12, and we’re making some simple updates to how we ship Clarity Angular to align better with Angular’s release cycle.
We’re excited to announce Clarity Angular has a new version available, with Angular 12 support! This anticipated release is easy to install, run the following with the Angular CLI to update your Clarity Angular packages to the latest release that will work with Angular 12:
ng update @clr/angular@12This will update your Clarity Angular packages to the latest release that will work with Angular 12.
Why the version change?
We are releasing the next major version of Clarity Angular as version 12, which skips a few numbers ahead to align with Angular version numbering. Aligning versions with Angular has the advantage of making it clearer which version of Clarity Angular and Angular are compatible.
When we released Clarity Angular v1 several years ago, we similarly updated our release cycle to match Angular’s releases. We will continue to update Clarity Angular to work with each new major Angular release.
What is new in Clarity Angular?
The only changes are related to updates for Angular 12 and TypeScript compatibility. There are no other breaking changes if you are updating from Clarity Angular v5. We will continue to fix and release patches for bugs in Clarity Angular on an ongoing basis as well.
If you haven’t seen our updated support strategy, rest assured that we are continuing to maintain and support Clarity Angular into the future as long as there is critical use. As part of that strategy, we also are not making major feature improvements and avoiding breaking changes to Clarity Angular, so it can be a long term stable platform for teams who are still using it.
What about Clarity Core?
We worked to separate our Clarity Core and Clarity Angular codebases, which will allow us to release each independently of one another. That means that Clarity Core will continue to release under v5.x release branches until we have a breaking change. We are working on a Clarity Core v6 later this year, but more will come on that later.
We’ve recently launched 7 new Core components into beta: Table, Tree View, Cards, Panel, Vertical Navigation, Breadcrumbs, and Navigation. Documentation about these can be found in our Storybook demo app, and we’ll be adding them to our main documentation site in the coming months. We’re currently working hard on the Datagrid and Dropdown components and expect the beta versions to arrive in the coming weeks.
Common questions
Let’s quickly address some of the common questions and concerns that we’ve been answering related to these changes.
- Is Clarity Angular being deprecated or abandoned? — In January we outlined our path forward with Clarity Angular and nothing has changed. We will not release any new components or major features in Clarity Angular, but we are continuing to support it with bug fixes and updates for major Angular releases. The goal is to ensure that Clarity Angular is as stable as possible so you can continue to use it as long as you need.
- Can I get the Angular documentation with interactive demos? — Yes, we are nearing completion of several efforts with our documentation, which will bring the original Clarity Angular website back with latest updates. Look for updates on this soon!
- Should I quit using Clarity Angular? — You can safely continue to use Clarity Angular as long as you need it. We recommend that you consider planning your journey for how you expect to evolve your application and anticipate how you can adopt Clarity Core on your own timeline to get the new features, better accessibility, and long term stability. If you start with a new website today, we recommend using as much from Clarity Core as you can, and fill in with Clarity Angular if needed until we have finished Clarity Core components.
By fully separating Clarity Core and Clarity Angular, we have a better path forward to support our communities while also innovating for our framework independent goals. It is going to enable us to move faster, to more easily document things, and make it easier to support applications looking to transition from Clarity Angular to Clarity Core on their own timeline.
