Skip to content

Replies

0
Yannick Löffler
Yannick Löffler answered on Jan 19, 2022 6:57 AM

Hey guys,

looks like you patched an error into the migration script of the latest 12.x.y versions.

An update to the previous version 11.1.38 -> 12.0.11 works.

from 12.0.11 I was able to update to the latest 12.3.9

That works for me. I hope that helps other users, too!

0
Yannick Löffler
Yannick Löffler answered on Jan 18, 2022 4:07 PM

Looks like the screenshot didn't work…. here comes the error as a text

ng update @infragistics/igniteui-angular@12 -C --force
Using package manager: 'npm'
Collecting installed dependencies...
Found 50 dependencies.
Fetching dependency metadata from registry...
    Updating package.json with dependency @infragistics/igniteui-angular @ "12.3.9" (was "11.1.38")...
  UPDATE package.json (2139 bytes)
√ Packages successfully installed.
  Committed migration step (573efb49c): Angular CLI update for packages - @infragistics/igniteui-angular@12.
** Executing migrations of package '@infragistics/igniteui-angular' **

> Updates Ignite UI for Angular from v11.1.x to v12.0.0.
    Applying migration for Ignite UI for Angular to version 12.0.0
    Installing temporary migration dependencies via npm.
    Adding 'angularCompilerOptions.strictTemplates' to tsconfig.json for migration run.
× Migration failed: Cannot read property 'escapedName' of undefined
  See "C:\Users\xyz\AppData\Local\Temp\ng-CuG3JR\angular-errors.log" for further details.

0
Yannick Löffler
Yannick Löffler answered on Feb 23, 2021 2:31 PM

Hello again,

we removed the mask as suggested. This workaround is sufficient for us at the moment – thank you!