Confused an editor build with an editor implementation Read more in the Installing plugins guide. In this situation, webpack will know that it only needs to load each plugin once. Therefore, you must never add plugins to an existing build unless your plugin has no dependencies.Īdding plugins to a build is done by taking the source version of this build (so, before it was built with webpack)Īnd adding plugins there. Included inside the build package, and second, because they are required by the Highlight plugin. If you ask webpack toīuild such a project, you will end up with the modules being included (and run) twice – first, because they are

and the Highlight plugin imports some of the modules from these packages, too. That it contains all the necessary code from e.g. The build package contains a file which is already compiled with webpack. If you import an existing CKEditor 5 build and a plugin like this: import ClassicEditor from Highlight from your project loads some CKEditor 5 packages twice. Trying to add a plugin to an existing build

You may need to check your project for each of these issues and fix them all. There are many situations in which some modules can be loaded twice. Module duplication leads to inevitable runtime Of its modules were duplicated (evaluated and executed twice). This error is thrown when due to a mistake in how CKEditor 5 was installed or initialized, some

Javascript array remove empty slots