I've seen that this project is no longer maintained, but I wanted to share this experience nonetheless, so other people are aware of this.
When I specify typescript as a proptype it won't use it, but instead will (wrongfully) fall back to other registered plugins. I've made a demo repo where you can see this behavior. It also implements a native highlight solution, bypassing this component entirely.
Since this package is no longer maintained and the work-around is so simple. Maybe it is an idea that this plugin no longer should be recommended on the Readme of highlight.js?
I've seen that this project is no longer maintained, but I wanted to share this experience nonetheless, so other people are aware of this.
When I specify typescript as a proptype it won't use it, but instead will (wrongfully) fall back to other registered plugins. I've made a demo repo where you can see this behavior. It also implements a native highlight solution, bypassing this component entirely.
Since this package is no longer maintained and the work-around is so simple. Maybe it is an idea that this plugin no longer should be recommended on the Readme of highlight.js?
You can clone the repo below to get a minified code-sample of the situation I'm describing. https://github.com/JeffreyArts/demo-bug-vue-highlight-js