websdk-1019-upgrade

To migrate your Cumulocity Web SDK project from 1018 to 1019, you must upgrade to Angular 16 and switch from c8ycli to @angular/cli. The process involves scaffolding a new project, transferring source files, and aligning configurations.

You need to switch from c8ycli to ng-cli because the Cumulocity Web SDK 1019 upgrade mandates the transition to @angular/cli to properly support Angular 16 features and tooling. This requires scaffolding a new project structure and migrating existing code.

When upgrading to Web SDK 1019, you must update your package.json and cumulocity.config.ts files. You also need to verify your tsconfig setup and resolve peer dependency issues to ensure Angular 16 compatibility.

To resolve peer dependency issues during your Angular 16 upgrade, you must align your project's package.json dependencies with the new Angular 16 compatibility requirements. This involves updating package versions and verifying your tsconfig configuration.

Yes, you can keep your existing source files when migrating to Cumulocity Web SDK 1019. The migration process involves scaffolding a new Angular 16 project structure and then transferring your existing source files into it before adjusting configurations.

The best way to scaffold a new project for Cumulocity Web SDK 1019 is to use @angular/cli instead of c8ycli. This creates a standard Angular 16 project structure where you can transfer your source files and update your package.json and cumulocity.config.ts.