Plan for angular 12 upgrade

[sushan05]

What are the plans for angular 12 upgrade and enabling Ivy ?

[ph55]

Yes, can we get issue to track please?

[bbogdanov]

@mathisloge The ng add command is fixed and should be working just fine.

We also released v12 as stable so you could give it a try with ng add @clr/angular on a project with Angular 12.

Let us know if you face any issues.

[mathisloge]

nice. thanks for notifying me. Will report if i face any issues.

[bbogdanov]

@ph55 @sushan05 @kumart-netapp @dpsarrou Angular 12 support was released as stable yesterday. https://www.npmjs.com/package/@clr/angular/v/12.0.0

Let us know if you face any issue.

[kumar-tadepalli]

@bbogdanov
What is the version number clarity is going to follow?
Is Clarity aligning with angular version for @clr/* package?
How do we co-relate @cds/core version which is v5.4.3 now?

Basically in my project is not using @cds/core, it is @clr/* based once. But we have to include in package.json to make compiler happy and avoid below error:

Error: ./node_modules/@clr/angular/ivy_ngcc/fesm2015/clr-angular.js
Module not found: Error: Can't resolve '@cds/core/icon' in 'C:\Users\admin\repo\WS\ui\node_modules@clr\angular_ivy_ngcc_\fesm2015'
resolve '@cds/core/icon' in 'C:\Users\admin\repo\WS\ui\node_modules@clr\angular_ivy_ngcc_\fesm2015'
Parsed request is a module
using description file: C:\Users\admin\repo\WS\ui\node_modules@clr\angular\package.json (relative path: ./ivy_ngcc/fesm2015)
Field 'browser' doesn't contain a valid alias configuration
resolve as module
looking for modules in C:/Users/admin/repo/WS/ui/src
using description file: C:\Users\admin\repo\WS\ui\package.json (relative path: ./src)

[bbogdanov]

@shravansofts

We are writing a blog post where we are going in details about what we are doing with @clr/angular. @gnomeontherun could give you more details when it will be available.

Basically @clr/* is aligning with angular version, so you guessed that correctly. We are going to support every Angular version until we recreate all our components in Clarity Core.

Clarity Core is going to follow its own versioning and we are going to release v6 in near future.

On the other hand, After @clr/angular@>=5.0.0 @clr/angular depends on @cds/core for the icons so @cds/core is a required package to have if you want to use Clarity Angular v5 and above. @clr/icons is deprecated and it won't be supported anymore. You can learn more about @clr/icons deprecation here