The Markdown Typescript code parser is bailing on a very specific snippet containing generics and a lambda arrow

[ChristianIvicevic]

• VSCode Version: 1.39.1
• OS Version: Windows x64 10.0.17763

Steps to Reproduce:

1. Create a new Markdown file
2. Add the following snippet

```typescript
const array = [1, 2, 3].reduce<number[]>((acc, next) => [...acc, next], []);
//                             ~~~~~~~~
// Type of the initial value, in our case making it an array of numbers.
```

Doing so will make the formatter bail and the comment below won't be recognized as a comment:

However when removing the arrowhead of the lambda it works as expected:

Does this issue occur when all extensions are disabled?: Yes

[mjbvz]

This is in the markdown preview, correct? The highlighter in the markdown preview uses highlightjs by default.

Please file an issue against that project: https://github.com/highlightjs/highlight.js

[ChristianIvicevic]

@mjbvz Alright, thanks for pointing me in the right direction. On a slightly different "off"topic, I stumbled upon highlightjs myself yesterday since I am moving from Markdown to Asciidoc and noticed their Typescript highlighting isn't too advanced yet (only keywords, built ins, strings and numbers are highlighted, no members, function invocations, parameters or 3rd party types) in comparison to Githubs Markdown highlighting. Let's see whether I can contribute there to improve upon that a bit.

[ChristianIvicevic]

Here is the new issue for anybody noticing the same problems: highlightjs/highlight.js#2189