Update to Angular 16

As part of the continuous improvement efforts, we are updating all our front-end frameworks to the latest Angular major release version (16).

The following table shows the LTS Ends dates for the current Angular releases:

Angular 16 Support

The official WebMap packages versions that are compatible with Angular 16 are:

Repository

Name

Version

AngularClient

@mobilize/angularclient

12.0.0

BaseComponents

@mobilize/base-components

11.0.0

WFNetKendoComponents

@mobilize/winforms-components

12.0.0

WebFormsComponents

@mobilize/webformscomponents

5.0.0

WFNetJanus

@mobilize/jns-winforms-components

8.0.0

WFNetAccess

@mobilize/acs-winforms-components

3.0.0

WFNetC1Components

mobilize/wfnet-c1-components

5.0.0

Update Existing Projects to Angular 16

Updating an already migrated project you should follow this process:

  1. Install Node.js, version 16.20 or above is required

    1. Download the latest Node.js release from its official download page and install the new Node.js release.

    2. If you have problems with latest version, use this instead 16.20.2.

  2. You must update your angular/cli version to version 16

    1. First uninstall your current version with command and clean cache:

yarn global remove @angular/cli or npm uninstall -g @angular/cli

yarn cache clean or npm cache verify

3. Install the 15 version:

yarn global add @angular/cli@16.2.14 or

npm install -g @angular/cli@16.2.14

Project updates can be performed both manually or using the Angular CLI Tool.

Migrating to Angular 16 Automatically

The first recommendation is to generate your new Angular 16 upgraded code through the Conversion Tool same as the first time.

You can also use the Angular CLI tool to migrate your WebMap project automatically from Angular 15 to 16.

To perform the update, you need to follow the official Angular Update Guide provided by Angular.

Compile the migrated application

Compile your migrated application with ng build, also you can compile with ng build --configuration=production for the production mode.

  1. Maybe you going to need more RAM for the compilation process, please use node --max_old_space_size=8192 ./node_modules/@angular/cli/bin/ng build to assign 8 GB of RAM.

Since the update to Angular 13 we also moved from the deprecated TSLint (https://www.npmjs.com/package/tslint) to ESLint (https://www.npmjs.com/package/eslint) and enable the Prettier code formatter for our components frameworks to keep a clean and tidy code.

To take full advantage of these changes we strongly recommend you install some extensions for your Visual Studio Code:

With these extensions you will be able to format your code according the expected ESLint standard. Also, it will report you directly on the editor any possible error that you introduce in the code files.

Last updated