ckeditor5-image | Image feature for CKEditor | Computer Vision library

As you stated, there are several major time consuming problems to be solved with approach that you took. Key to a successful email template is compatibility with many different email clients. Email clients support archaic HTML tags, such as

If I were you (and if CKEditor doesn't have email templating), I'd post the template you created to some of the freelancer platforms out there and say 'guys, how much to convert this HTML to email compatible HTML'. That's the fastest and cheapest way. Test resulting code by sending it in email and checking it out in different email clients.

Other way is for you to get to know what creating HTML and styling for emails is all about. Good starting point is to analyze (and perhaps reuse) HTML from HTML emails that you received from, let's say, your local cell service provider. You'll need to do a research on the topic to find out what suits your needs, but here are some basic guidelines:

• supported HTML tags in emails
• step-by-step guide to creating email templates

So this popup becauseof the conflict version of ESLint in my package.json and in ckeditor5 ( which i forked ) is different.

Anyway, if you want to build a custom like me

1. Fork all the repo.
2. Create your custom build but dont push it into the repo which you forked.
3. Instead create a new reposity, push your custom build into there.
4. Install it via

After testing, I found that EssentialsPlugin must be import.

App.vue

OK, finally figured it out. The problem was in all the plugins with version 18.0.0

I guess they were the ones duplicating some modules. Once downgraded to version 15.0.0 - it all worked as it should!

Here's a link to GitHub repo

And to npm package

As I've answered in the https://github.com/ckeditor/ckeditor5/issues/1831:

As you can see at the source code of the NormalModuleReplacementPlugin the regexp is tested two times, once before the resolution on the request and once after the resolution on the resource.

As you might see most of the times your function is called after the resolution (as the requests don't match the regexp). The request after the resolution is enhanced by the loaders (that's why the paths are so long and contain weird characters) and actually, this option isn't used anymore. That's why you should change the result.resource instead of the result.request.

E.g. try the following plugin:

import ImageLibrary from './js/image-library.js';

You don't export that library from a file, so that's why you have an error Cannot read property 'pluginName' of undefined. The ImageLibrary in the ckeditor.js becomes the undefined as it's can't be found in the image-library file.

Turns out I just need to add