Josh Goebel

Depending on your needs it's easy enough to fire up TWO entirely different Wren VMs... and one can call into the other - since it's not reentrancy at that point....

Not immediately clear this is a problem with the plugin vs your setup/packaging? Can you confirm if this is a JS or CSS issue at least?

> The reason is that webpack did not pack the unused code when packing, so quotes it here. HLJS is not unused, it's imported then used... or are you referring...

I can only read English.

Would this just be a docfix then to say that in some cases you may need to use the module to make sure it isn't tree-stripped?

I wonder if we could just add a few more values to the `sideEffects` key in package.json?

Sounds like some sort of build problem... maybe? The highlighting shouldn't be different unless something at the JS level was different between your two environments. Maybe looking closely at your...

What languages do you usually see getting chosen?

Maybe add some debugging to output the value of `hljs.listLanguages()` and see what that returns just to confirm you're loading them all.

It looks to me (reading source) that setting language should override the autodetect prop, am I missing something?