v5.0.4

Bug fixes

• The <CKEditor> component does not emit an error when destroying the context feature. Closes #349, #339. (commit)

v5.0.3

Bug fixes

• Fixed the component initialization procedure to enforce cleanup completion before subsequent editor initialization. Closes #321, #338. (commit)

  Thanks to @corymharper.

v5.0.2

Other changes

• Upgraded the @ckeditor/ckeditor5-watchdog package to the latest version. (commit)

v5.0.1

Bug fixes

• Fixed component double rendering in StrictMode. Closes #294. (commit)

v5.0.0

BREAKING CHANGES

• Due to introducing the lock mechanism for the Editor#isReadOnly property, the <CKEditor> component uses the new way of enabling the read-only mode in the editor. The component requires an instance of CKEditor 5 in version 34 or higher. See ckeditor/ckeditor5#10496.

Other changes

• Aligned the <CKEditor> component API to use the new lock mechanism when enabling/disabling the read-only mode. (commit)

v4.0.1

Other changes

• Bumped Karma test runner to v6.x. Closes #292. (commit)
• Support for React 18. Closes #297. (commit)

v4.0.0

BREAKING CHANGES

• 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

• Updated the required version of Node.js to 14. See ckeditor/ckeditor5#10972. (commit)

v3.0.3

Internal changes only (updated dependencies, documentation, etc.).

v3.0.2

Bug fixes

• Make sure that the watchdog instance exists before destroying itself. Closes #197. (commit)

v3.0.1

Other changes

• Added React@^17 as allowed version in peerDependencies. (commit)