After the update to 2.2.1 today, the code is telling me I need to allow 'unsafe-eval' for scripts-src and that the plugin is not available.
Due to security reasons, we cannot enable 'unsafe-eval' for all scripts and were very happy when CKEditor5 no longer required this exception.
Any advice on getting this codebase working without enabling 'unsafe-eval'? Everything worked great before todays updates.
Uncaught EvalError: Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the Content Security Policy directive".
at ./js/ckeditor5_plugins/editorAdvancedLink/src/index.js (editorAdvancedLink.js?v=10.1.0:1:17738)
at __webpack_require__ (editorAdvancedLink.js?v=10.1.0:1:21635)
at editorAdvancedLink.js?v=10.1.0:1:22114
at editorAdvancedLink.js?v=10.1.0:1:22268
at editorAdvancedLink.js?v=10.1.0:1:243
at editorAdvancedLink.js?v=10.1.0:1:248CKEditorError: plugincollection-plugin-not-found {"plugin":null}
Read more: https://ckeditor.com/docs/ckeditor5/latest/support/error-codes.html#error-plugincollection-plugin-not-found
at ckeditor5-dll.js?v=38.0.1:5:96606
at ckeditor5-dll.js?v=38.0.1:5:96665
at Array.forEach (<anonymous>)
at u (ckeditor5-dll.js?v=38.0.1:5:96467)
at l.init (ckeditor5-dll.js?v=38.0.1:5:94955)
at D.initPlugins (ckeditor5-dll.js?v=38.0.1:5:101705)
at js_SEFLuXsaL76H0OSY66vqxSdMZ03nuVk3JNHVcy-EKgY.js?Fixed
2.2
Code
Issue #3370300: commit production build.
Thank you for reporting this issue!
I committed the dev build of the JS file... This will be fixed in the upcoming 2.2.2 version.
I added a security so it doesn't happen again.
Sorry for the inconvenience.
Automatically closed - issue fixed for 2 weeks with no activity.