All Versions
Latest Version
Avg Release Cycle
108 days
Latest Release
103 days ago

Changelog History
Page 1

  • v4.0.0 Changes

    February 09, 2022


    • โฌ†๏ธ Upgraded the minimal versions of Node.js to 14.0.0 due to the end of LTS.

    ๐Ÿ› Bug fixes

    • ๐Ÿ‘‰ Use async/await in CKEditorContext#_destroyContext() to handle context destruction properly. Closes #283. (commit)

    Other changes

  • v3.0.3 Changes

    October 05, 2021

    ๐Ÿ“š Internal changes only (updated dependencies, documentation, etc.).

  • v3.0.2 Changes

    March 08, 2021

    ๐Ÿ› Bug fixes

    • ๐Ÿ‘‰ Make sure that the watchdog instance exists before destroying itself. Closes #197. (commit)
  • v3.0.1 Changes

    February 09, 2021

    Other changes

  • v3.0.0 Changes

    October 28, 2020


    • The onInit property was renamed to onReady and can be called multiple times (after the initialization and after the component is ready when an error occurred).
    • ๐Ÿ“ฆ The entry point of the package has changed. The default import was removed since the package provides more than a single component now. Use

      import { CKEditor } from '@ckeditor/ckeditor5-react';

      instead of

      import CKEditor from '@ckeditor/ckeditor5-react';

    ๐Ÿ”‹ Features

    • Support for the config.initialData option in the configuration object when creating the <CKEditor> component. When passing the [data] property and the initialData value in the configuration object, the later one will take precedence and a warning message will be logged on the console. (commit)
    • โœ… The <CKEditor> component contains the built-in watchdog feature. Closes #118. (commit)
    • โœ… Introduced the <CKEditorContext> component that supports the context feature. (commit)
    • โž• Added the id property which is used to distinguish different documents. When this property changes, the component restarts the underlying editor instead of setting data on it, which allows e.g. for switching between collaboration documents and fixes a couple of issues (e.g. the onChange event no longer fires during changing the document). Closes #168, #169. (commit)
    • ๐Ÿš€ The onError() callback will be called with two arguments. The first one will be an error object (as it was before the release 3+). A second argument is an object that contains two properties:. (commit)

      • {String} phase: 'initialization'|'runtime' - Informs when the error has occurred (during the editor/context initialization or after the initialization).
      • {Boolean} willEditorRestart - When true, it means that the editor component will restart itself.
      • {Boolean} willContextRestart - When true, it means that the context component will restart itself.

      The willEditorRestart property will not appear when the error has occurred in the context feature. The willContextRestart property will not appear when the error has occurred in the editor.

    Both components (<CKEditor> and <CKEditorContext>) will internally use the Watchdog class that restarts the editor or context when an error occurs.

  • v2.1.0 Changes

    January 16, 2020

    ๐Ÿ”‹ Features

    ๐Ÿ‘ Introduced support for onError callback that is being called if an error occurred during the editor's initialization. Closes #123. (becf9f7)

    Thanks to @ansorensen.

  • v2.0.0 Changes

    November 22, 2019

    Other changes


    • ๐Ÿ‘€ <CKEditor> React component is now distributed in ES6 instead of ES5. See #105.
  • v1.1.3 Changes

    April 01, 2019

    ๐Ÿ› Bug fixes

    • โšก๏ธ The <CKEditor> component will not update anything until it is not ready. Closes #83. (63cb97d)
  • v1.1.2 Changes

    March 26, 2019

    ๐Ÿ› Bug fixes

    • โšก๏ธ The <CKEditor> component will not be updated by the React itself. The editor won't freeze if the #data property was specified as a static string. Closes #75. Closes #78. (bdb2ce3)
  • v1.1.1 Changes

    February 28, 2019

    ๐Ÿ› Bug fixes

    • ๐Ÿ›  Fixed integration with collaboration features by changing the way how the initial data are passed to an editor instance. Previously the <ckeditor> component had been using the editor.setData() method which produces invalid results in collaboration. Now the initial data are injected directly into the container on which the editor will be created. Closes #68. (1c93b3e)

    Other changes