Ghislain B.

Pull Requests to add features are always welcome...

this would have to most probably be implemented in the `bootstrap-markdown` editor library which is outside of current lib, so I'll close as won't fix

If you want to help and provide Pull Requests to update necessary stuff, I'd be happy to cut a release afterward. I just don't have the bandwidth to work on...

looking at the `package.json` and I guess that `core-js` and `vinyl-paths` can simply be moved from `dependencies` to `devDependencies` or simply be removed and that would fix the security issues....

the change is done, see new [v3.0.0](https://github.com/ghiscoding/angular-markdown-editor/releases/tag/v3.0.0) release

If you have time to debug it, that would help because I don't currently have the time to look into it. What I could say though is that the problem...

@stefanwalther I'll be more than happy to receive any PRs to fix the issue you mentioned.

@danielelkington Adding your fork into my project and I can see that it also adds `custom-event-polyfill` in the lib's [package.json](https://github.com/danielelkington/vue-shortkey/blob/release/package.json) and I understand this polyfill was necessary in Vue 2...

I had the same problem when I realized that the default font was using `Font-Awesome` which I didn't have. If you don't have `Font-Awesome` installed, which you don't seem to...

A bit late on the show, but here are some thought. @waggyman @lodev09 If you want to support BS3 and BS4 (which you should since a lot of us didn't...