highlightjs/highlight.js

Support Lezer grammars with our output pipeline

Open

#3,623 opened on Sep 14, 2022

View on GitHub
 (1 comment) (1 reaction) (0 assignees)JavaScript (22,960 stars) (3,497 forks)batch import
enhancementgood first issuehelp welcomeparser

Description

It'd be nice to be able to use Lezer for parsing paired with our output pipeline... this would allow users wishing to pay a higher download cost to get much improved support for some languages that require a more complex parsing engine.

References:

Contributor guide

Tech stack
javascript
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
highlight.js output pipelineLezer grammar basicsJavaScriptParsing concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
This feature request involves integrating the Lezer parsing system with highlight.js's output pipeline. To get started, review the linked issues (#3619, #3620) and the Lezer documentation (https://lezer.codemirror.net/docs/guide/). The main challenge is understanding how to map Lezer's parse tree to highlight.js's existing tokenization and output mechanisms. There are currently no assignees or linked PRs, so this issue is open for exploration. A good first step would be to prototype a proof of concept for a single language to validate the approach.
Support Lezer grammars with our output pipeline · highlightjs/highlight.js#3623 | Good First Issue