CKEditor Supports Bower and Composer

Since version 4.3.3 CKEditor supports two popular package managers, Bower and Composer. They can be used to install CKEditor releases and keep them up to date in the same way that you maintain other dependencies of your project.

Installed Preset

Both package managers will install the standard-all CKEditor preset that includes all official CKSource plugins with only those from the Standard installation package compiled into the ckeditor.js file and enabled. See here for a comparison of packages.

Additional plugins included in the standard-all preset can be enabled in your configuration by using the config.extraPlugins option.

Tag Changes

Please note that package managers compatibility also meant that the tags used in our ckeditor-releases repository have changed to follow the Semantic Versioning 2.0.0 format.

Since version 4.3.3 this repository uses the following tag naming rules:

• x.y.z – contains the standard-all editor build, e.g. 4.3.3, 4.4.0, etc.
• (basic|standard|full)/x.y.z – contains the editor build with a given preset, e.g. basic/4.3.3.

Custom Configuration & Updates

If you want to use any of the package managers to keep CKEditor up to date, your custom editor configuration should not be done in any of the core CKEditor files like config.js (otherwise you risk overwriting them during the update process).

It is thus recommended to use of the following strategies:

• Defining configuration in-page.
• Using a custom configuration file.

Both options are explained in more detail in the Setting CKEditor Configuration article.

Usage Instructions

Read the new Installing CKEditor with Package Managers article in CKEditor Developer's Guide to learn how to fetch CKEditor using Bower or Composer.