(chore) Fix typescript type exports

[joshgoebel]

Resolved #2945.

Changes

Checklist

• Added markup tests, or they don't apply here because...
• Updated the changelog at CHANGES.md

[Hypnosphi]

@joshgoebel can you please backport this into v10? I'd be happy to migrate to v11, but unfortunately I can't, because I use dynamic imports, see webpack/webpack#13865

[joshgoebel]

V10.0 is about to drop off the supported list entirely. The core team really does not have time to support multiple versions. Even a PR here isn't super trivial as it would have to pull over the new changes but then also back out the changes to types that occurred between 10 -> 11.

but unfortunately I can't, because I use dynamic imports, see webpack/webpack#13865

import isn't the only way to use the library. You could use the stand-alone JS builds (as a separate file even) or even append our web build at the very end of your build process (I'm sure Webpack has a way of doing this). So there are ways to use v11 with Webpack despite the bug.

[joshgoebel]

If the exports was a huge issue we might perhaps drop them entirely, but it seems only a few broken tools are having issues and that mostly everything else works - unless others would like to chime in here.

[Hypnosphi]

More context: we're developing a component library, and our Code component loads languages on demand in runtime depending on the passed language prop value. How would I do that without using dynamic imports or migrating away from webpack?

Source: https://github.com/JetBrains/ring-ui/blob/typescript/components/code/code.tsx#L15-L21

[joshgoebel]

Well, I'm not a webpack person I have no idea what the magic comment is trying to do but I'd imagine for dynamic run-time dependencies (via import) you would just use the new ESM CDN builds that we publish (as of 11.2) unmodified... the grammars are all package up in individual files for dynamic usage... and the "main" Highlight.js bundle could be:

• loaded separately via <script>
• concated to the end of your webpack build (surely there exists a web pack plugin to do this)
• imported dynamically as well (via ESM CDN build)