Update framework integrations to ESM #16616
Labels
resolution:resolved
This issue was already resolved (e.g. by another ticket).
squad:core
Issue to be handled by the Core team.
type:bug
This issue reports a buggy (incorrect) behavior.
Comments
filipsobol
added a commit
to ckeditor/ckeditor5-vue
that referenced
this issue
Jul 11, 2024
Fix: Use type of the passed `editor` prop rather than generic `Editor` type. Closes #282. Internal: Migrate from webpack and Karma to Vite and Vitest. See ckeditor/ckeditor5#16616. MINOR BREAKING CHANGE: Migrate to ESM. See ckeditor/ckeditor5#16616. MINOR BREAKING CHANGE: Migrate to Composition API. Closes #172. MINOR BREAKING CHANGE: Bump required version to Vue 3.4+. See #282. MINOR BREAKING CHANGE: Export the component as `Ckeditor` instead of `default.component`. Closes #284. MINOR BREAKING CHANGE: Remove argument from the `destroy` event, as it was always `null`. Closes #283.
filipsobol
added a commit
to ckeditor/ckeditor5-react
that referenced
this issue
Jul 12, 2024
Internal: Migrate from webpack and Karma to Vite and Vitest. See ckeditor/ckeditor5#16616. Internal: Fix test coverage which only covered a small portion of the codebase. MINOR BREAKING CHANGE: Migrate to ESM. Related to ckeditor/ckeditor5#16616.
Witoso
added
squad:core
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After we migrated the editor to ESM, there appear to be an issue with our React and Vue integrations, which still use UMD and thus
require.We need to update these two integrations to use ESM too.
Related issue: ckeditor/ckeditor5-react#475
The text was updated successfully, but these errors were encountered: