CKEditor5 DLL build is deprecated and will be EOL by the end of 2025 (https://ckeditor.com/docs/ckeditor5/latest/updating/nim-migration/migrat...).
The DLLs will be supported until the end of 2025.
What we will sunset on this date:
- The documentation for DLLs will be removed.
- New versions of npm packages published after this date will not have build directory. It will not be possible to import files from those destinations.
Use the new installation method
- Published in the 42.0.0 version (released July 2024).
- Provide many improvements: work well with all modern bundlers (i.e. bundler-agnostic), decoupled styles from the JavaScript layer.
- Two ways of self-hosted setup:
- aggregated packages: Use two packages that include everything, for easy onboarding.
- optimized way: Use individual packages for size-tuned builds.
- Two ways of cloud (CDN) hosting:
- UMD globals.
- ESM (import maps).
Decide whether to use UMD globals/ESM
Decide whether to keep webpack or use a different bundler
Migrate the import paths in ckeditor5 plugins
Update ckeditor5 libraries assets
Since the new installation method is not compatible with the DLL build, contrib modules need to provide plugins with the new installation method. I'm not sure how we're gonna handle this.
Active
11.0 🔥
ckeditor5.module
I have a proof of concept from last year that successfully does this, and the CK team + several committers were in support of the approach. The biggest part will likely be finalizing ✨ Add an API for importmaps Active , after which most of the CK changes are not too intense.
I also created a doc that details the approach and provides steps for several contrib modules on how to approach it
