lezer-parser/lezer

Issues

• Extend bundler support to Webpack and Vite using Unplugin

  #48 opened 8 months ago by illright
  1

• what is the npm package of the lazer

  #47 opened 9 months ago by jiangxiaoqiang
  1

• tree.children is undefined in @lezer/common

  #46 opened 9 months ago by gtm-nayan
  5

• Add a printer package

  #45 opened 9 months ago by deemp
  4

• generator runs out of memory on large grammar

  #44 opened 9 months ago by nchen63
  1

• Ignore/skipped tests?

  #43 opened 10 months ago by vanillajonathan
  2

• Speeding up build parser

  #42 opened 10 months ago by nchen63
  3

• Running lezer-generator on a complex grammar results in an error "Goto table too large"

  #6 opened 4 years ago by poeschko
  6

• Generated `specialized` field is not compatible with typescript strict mode

  #41 opened a year ago by berekuk
  4

• Types are broken when used with node16/nodenext

  #39 opened a year ago by berekuk
  2

• [generator] dist/rollup-plugin-lezer.cjs is missing in v1.4.1

  #40 opened a year ago by hubgit
  2

• Can't resolve 'process/browser'

  #38 opened a year ago by Dazaer
  4

• How to get usable error messages?

  #37 opened a year ago by unleashy
  3

• Version 1.2.1 of @lezer/generator tokenizes differently

  #36 opened a year ago by viktor-berglund-mw
  2

• Token parsing behavior change in generator between 1.2.0 and 1.2.1

  #35 opened a year ago by r3c
  2

• generator not importable from esm module

  #30 opened a year ago by allain
  5

• Concise API for getting text of a node/token?

  #34 opened a year ago by TedDriggs
  1

• Large grammar causes error "Tokenizer tables too big to represent with 16-bit offsets"

  #33 opened a year ago by nedgrady
  4

• PHP conflicts with Parcel watch mode: probably worth adding `require` to `KEYWORDS`

  #32 opened a year ago by ashmind
  0

• Potentially missing grammar for javascript tokenizer (Symbol.iterator)

  #31 opened 2 years ago by kdog3682
  1

• Question: How to query "syntax tags" for a given Node/NodeType?

  #29 opened 2 years ago by joshgoebel
  19

• Help contributing?

  #28 opened 2 years ago by drwpow
  3

• Rollup/yarn 2 plugin import error

  #2 opened 2 years ago by jeeger
  5

• Sandbox is not working

  #23 opened 2 years ago by b04505009
  2

• Bug: parse fails when text contains many "skip" nodes

  #24 opened 2 years ago by JuneKelly
  13

• Is it really this difficult?

  #27 opened 2 years ago by pragdave
  1

• generator creates invalid code

  #26 opened 2 years ago by BryanCrotaz
  5

• `firstChild` missing

  #25 opened 2 years ago by joelburget
  1

• Grammar railroad diagram

  #22 opened 2 years ago by mingodad
  6

• Does Lezer support (or plan to support) local variables?

  #7 opened 2 years ago by jason5122
  3

• Consider using a monorepo

  #1 opened 2 years ago by Timmmm
  1

• Unterminated string handling regex can hang lezer-generator due to exponential backtracking

  #21 opened 2 years ago by briangough
  2

• Feature request: match quotes

  #20 opened 2 years ago by pmg23
  1

• Incorrect node nesting

  #19 opened 2 years ago by unconed
  1

• Typings for Tree.resolve changed in `0.15.11`

  #18 opened 3 years ago by paddyobrien
  1

• Proposal: a mixed-language interface accessible within ExternalTokenizer instances

  #17 opened 3 years ago by ashtonsix
  4

• Inline terms not exported

  #16 opened 3 years ago by ashtonsix
  2

• SyntaxError: No parse at x

  #15 opened 3 years ago by milahu
  3

• Infinite loop in recovery

  #13 opened 3 years ago by backmask
  4

• Consider alternative approaches to forced reduction

  #14 opened 3 years ago by marijnh
  0

• Feature Request: Add Objective-C parser

  #12 opened 3 years ago by bhamiltoncx
  1

• Generator could generate ts file

  #11 opened 3 years ago by Nexucis
  2

• Query a syntax tree, – a la Tree-Sitter.

  #10 opened 3 years ago by c4lliope
  2

• Generating lezer grammar from tree-sitter grammar?

  #9 opened 5 years ago by ubolonton
  2

• Consider making node names exports rather than strings

  #8 opened 4 years ago by marijnh
  5

• Profile and optimize

  #5 opened 5 years ago by marijnh
  1

• Extending a predefined grammar.

  #4 opened 3 years ago by s0kil
  1

• Consider supporting a 'compress' action on stacks

  #3 opened 3 years ago by marijnh
  0