Javascript family leaving 'template' span open after particular earlier syntax

[danopia]

Information

• Language: Javascript, also Typescript
• Plugins: Whatever the test page uses, presumably none

Description

I found a highlighting bug in this source code: https://deno.land/std@0.79.0/encoding/toml.ts and when the latest version of PrismJS was tested it showed a different bug. So I'm reporting the bug from latest here, from copying the whole file into Prism's test page.

It seems like particular template literal usage is getting parsed correctly earlier in the file, and then breaking other template tags later in the file. The affected line has its first template tag token ignored which then causes template tag parsing to be inverted for the rest of the file.

It seems there's two different setup lines for this bug that both need to be in a particular order:

1. One line with a regex containing a single quote, and then a single quote in template quotes. This renders fine.
2. Anywhere after that, a comment with a template literal in it. This renders fine.
3. Anywhere after that, a normal basic template literal. This breaks for the rest of the file

Code snippet

Test page

The code being highlighted incorrectly.

// One line with a pattern containing single quote, and then a single quote in template quotes
replace(/'/, `'`)

// Anywhere after that, a comment with template tags in it:
// `load bearing comment`

// Anywhere after that, normal basic template tags are broken
const var3 = `break starts here`;
const var4 = `break ends here`;

[RunDevelopment]

Thanks for reporting this!

This is a bug in Prism's matching algorithm for greedy rules. I'll try to fix it in the next couple of days.