Bump @ckeditor/ckeditor5-vue from 5.1.0 to 7.0.0

[dependabot[bot]]

Bumps @ckeditor/ckeditor5-vue from 5.1.0 to 7.0.0.

Release notes

Sourced from @​ckeditor/ckeditor5-vue's releases.

v7.0.0

We are excited to announce a new major release of the Vue integration.

In this release, we have introduced the following breaking changes that should make using the integration more intuitive and easier.

• Composition API: The integration has been rewritten in Composition API, which follows the recommended way of writing components in Vue 3.

• Vue 3.4+: The minimum required version of Vue is now 3.4+ because we are using the Generics and defineModel() features to provide better typings for the editor prop and component events.

• ESM-first: Besides the UMD build, the integration is now available in ESM format. In most projects, the new ESM build should be automatically prioritized by bundlers and other tools.

• Changed exports: We have changed how the Vue plugin and component are exported. The Vue plugin is no longer the default export but is exported as CkeditorPlugin. The component is now exported as Ckeditor instead of default.component.

  Here's a comparison of how you can import the Vue plugin that registers a global <ckeditor> component:

  // Before the release.
  import CKEditor from '@ckeditor/ckeditor5-vue';
  // After the release.
  import { CkeditorPlugin } from '@​ckeditor/ckeditor5-vue';
  

  If you prefer to use a local component instead of a global component, here's a comparison of how you can import it:

  // Before the release.
  import CKEditor from '@ckeditor/ckeditor5-vue';
  const component = CKEditor.component;
  // After the release.
  import { Ckeditor } from '@​ckeditor/ckeditor5-vue';
  const component = Ckeditor;
  

• Remove the editor argument from the destroy event: The destroy event no longer has an editor argument since it was always null.

• New name of the global variable: The name of the global variable used in the UMD build changed from CKEditor to CKEDITOR_VUE.

BREAKING CHANGES

• Bump required version to Vue 3.4+. See #282.
• Change the global name used in the UMD build from CKEditor to CKEDITOR_VUE.
• Export the component as Ckeditor instead of default.component. Closes #284.
• Migrate to Composition API. Closes #172.
• Migrate to ESM. See ckeditor/ckeditor5#16616.
• Remove argument from the destroy event, as it was always null. Closes #283.
• Rename main package exports to CkeditorPlugin and Ckeditor.

Bug fixes

• Change the global name used in the UMD build from CKEditor to CKEDITOR_VUE to match the new convention. See ckeditor/ckeditor5#16736. (commit)

... (truncated)

Changelog

Sourced from @​ckeditor/ckeditor5-vue's changelog.

7.0.0 (2024-08-07)

We are excited to announce a new major release of the Vue integration.

In this release, we have introduced the following breaking changes that should make using the integration more intuitive and easier.

• Composition API: The integration has been rewritten in Composition API, which follows the recommended way of writing components in Vue 3.

• Vue 3.4+: The minimum required version of Vue is now 3.4+ because we are using the Generics and defineModel() features to provide better typings for the editor prop and component events.

• ESM-first: Besides the UMD build, the integration is now available in ESM format. In most projects, the new ESM build should be automatically prioritized by bundlers and other tools.

• Changed exports: We have changed how the Vue plugin and component are exported. The Vue plugin is no longer the default export but is exported as CkeditorPlugin. The component is now exported as Ckeditor instead of default.component.

  Here's a comparison of how you can import the Vue plugin that registers a global <ckeditor> component:

  // Before the release.
  import CKEditor from '@ckeditor/ckeditor5-vue';
  // After the release.
  import { CkeditorPlugin } from '@​ckeditor/ckeditor5-vue';
  

  If you prefer to use a local component instead of a global component, here's a comparison of how you can import it:

  // Before the release.
  import CKEditor from '@ckeditor/ckeditor5-vue';
  const component = CKEditor.component;
  // After the release.
  import { Ckeditor } from '@​ckeditor/ckeditor5-vue';
  const component = Ckeditor;
  

• Remove the editor argument from the destroy event: The destroy event no longer has an editor argument since it was always null.

• New name of the global variable: The name of the global variable used in the UMD build changed from CKEditor to CKEDITOR_VUE.

BREAKING CHANGES

• Bump required version to Vue 3.4+. See #282.
• Change the global name used in the UMD build from CKEditor to CKEDITOR_VUE.
• Export the component as Ckeditor instead of default.component. Closes #284.
• Migrate to Composition API. Closes #172.
• Migrate to ESM. See ckeditor/ckeditor5#16616.
• Remove argument from the destroy event, as it was always null. Closes #283.
• Rename main package exports to CkeditorPlugin and Ckeditor.

Bug fixes

... (truncated)

Commits

• 550fa81 Release: v7.0.0.
• 2ee5bba Merge pull request #302 from ckeditor/release-20240807
• 063bd83 Changelog for v7.0.0.
• 5fc488a Docs: Changelog. [skip ci]
• b72b20b Added missing from option for changelog script.
• da8058c Release: v7.0.0-alpha.2.
• cf0b5f1 Merge pull request #298 from ckeditor/release-alpha-20241707
• dc855a3 Docs: Changelog. [skip ci]
• eba73a5 Merge pull request #295 from ckeditor/rename-global-name
• e2a9bbc Merge pull request #296 from ckeditor/fix-typings
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)