Syntax highlighting ‘specificity’ lower compared to text editors

[lifepeer]

I'm using the built-in Chroma syntax highlighter but it seems to lack specificity compared to let's say VSCode or Atom. Consider the following example in JavaScript:

As you can see, the output from Hugo/Chroma is limited in terms of how many different ‘elements’ it recognises.

This is confirmed by using the option pygmentsUseClasses=true and inspecting the classes it assigns to elements which are highlighted using different colours in text editors but the same once processed by Hugo/Chroma, for example ‘target’ and ‘offset’ both share the class="nx" even though one is a parameter and the other is a method. Another example is ‘this’ and ‘return’ which are both class="k".

This issue is even more striking if you use some other language like R, which looks like there's no syntax highlighting at all… :(

Is it possible to set up Hugo/Chroma to differentiate between such elements and assign them different classes, please?

[bep]

To get a fix for this, you need to open up an issue in the Chroma issue tracker: https://github.com/alecthomas/chroma/issues

[lifepeer]

Roger that, thank you.

In case someone comes across this and wants to follow the issue over at alecthomas/chroma.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.