Maciej Bukowski

Unfortunately, [the recent update of deps and internal tools for building the library](https://github.com/ckeditor/ckeditor5-angular/pull/183) didn't close this issue, but I checked that it should be possible to turn these warnings off...

> Can you tell if this was the reasons for your [production build to fail](https://github.com/ckeditor/ckeditor5-angular/issues/181#issuecomment-625127482)? Short answer: no. Our release script was using out-dated Angular utils, which built a library...

It looks like a duplicate of #215[.](https://github.com/ckeditor/ckeditor5-angular/issues/215.)

Hi! I'm aware that currently, it's not possible to make it an optional dependency. The Watchdog feature was built-in into the component so it can restart the editor inside the...

I'm marking it as a bug, though, ideally, it could be fixed on the jest's side.

Hi @xinwanc, Is there any error in the console? I guess that there was an error and the editor was recreated and some code for attaching the toolbar has run...

Hi, @ezintz! Thanks for the detailed issue. Do you use babel or some other tool that transpiles code? The error message (`Class constructor ClassicEditor cannot be invoked without 'new'`) looks...

You export the `ClassicEditor` class in the `core/ckeditor.ts`, so you should then import it in the component correctly. And you should import the `Component` from the angular's core. Are you...

ok :) Does the same error throw now? I'm also thinking about the TypeScript's transpilation. But it'd be weird. You could eventually try to use `target: "ES6"`

Good to now that there's an issue there. Glad to help you :)