Migration Guide

This section helps with the migration from one yFiles for HTML version to another.

This covers the most typical cases

Migrating from an Evaluation Version to a Distribution Version

When you switch from a yFiles evaluation version to the full, i.e., non-evaluation version of the library, make sure to completely replace all library files with the files from the full version downloaded from your customer account. Avoid any setup where files from the evaluation version and the non-evaluation version are mixed in any way. More information is shown in the section Migrating from an Evaluation Version to a Distribution Version.

Migration from an Older Version to a More Recent Version

To migrate your yFiles for HTML library to a more recent version you have to replace all files of the older version with the newer ones. For bugfix releases, this is usually sufficient.When upgrading to a new major version, there will be breaking API changes that will make your current code most likely not work with the new library. These changes are described below.The automatic source code conversion tool can assist you with this task and will reduce the time you’ll need to migrate your code. The tool works on JavaScript, as well as TypeScript files.

Migrating from UMD to ES Modules

Migrating from UMD to ES modules can be done using the tool in the /tools/umd-to-es-modules/ folder in the yFiles for HTML package. See the corresponding section for more information. This section also describes how to do the migration manually.