@ckeditor/ckeditor5-vue 8.0.0-alpha.0 on Node.js NPM

The ready, error, and destroy events can now be emitted multiple times during a component's lifetime when the watchdog is active.
By default, the editor is wrapped with a watchdog that automatically restarts it after a crash. As a result, these events may fire repeatedly — error after each crash, destroy for each crashed editor, and ready after each successful watchdog restart — rather than only once during the component's mount/unmount lifecycle.
Additionally, destroy is no longer emitted when the component unmounts before the editor finishes initializing (it now fires only when an actual editor instance is destroyed). If your handlers relied on @destroy to detect component unmount, use Vue's onBeforeUnmount lifecycle hook instead

You can now listen to the new @error event to catch and handle any errors that occur during editor initialization or at runtime (including errors automatically detected and reported by the Watchdog).
Full Watchdog support has been added to the <ckeditor> component:
- The editor is now automatically wrapped with CKEditor 5’s Watchdog (unless you explicitly pass disableWatchdog: true). This gives you automatic crash recovery, error detection, and editor restarts without breaking your Vue component.
- New watchdogConfig prop for the Watchdog integration. You can now pass a full configuration object to customize its behavior:
```
<ckeditor
  :watchdog-config="{
    crashNumberLimit: 5,
    minimumTimeBetweenCrashes: 1000,
    // any other Watchdog options...
  }"
  ...
/>
```

Significantly improved stability during rapid component destruction (e.g. fast route changes, v-if toggling, or Suspense scenarios).