Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / lezer-parser/lezer issues and pull requests
#60 - TreeCursor.iterate continues iterating over sibling nodes
Issue -
State: closed - Opened by peaffenzeller 4 months ago
- 8 comments
#59 - Introduce `@unexpected` and `@missing` Node Types for Error Handling
Issue -
State: closed - Opened by binhtran432k 6 months ago
- 6 comments
#58 - Error nodes - Regression in 1.3.13+
Issue -
State: closed - Opened by unconed 7 months ago
- 1 comment
#57 - Javascript keyword `eval` issue
Issue -
State: closed - Opened by drgrice1 7 months ago
- 3 comments
#56 - Is there no way to identify which missing token(s) triggered an error node?
Issue -
State: closed - Opened by stuffaboutpete 7 months ago
- 2 comments
#55 - Regression in 1.4.1
Issue -
State: closed - Opened by unconed 7 months ago
- 1 comment
#54 - Getting the term names for static type checking
Issue -
State: open - Opened by danielkleinert 9 months ago
- 2 comments
#53 - Incremental parsing of large document breaks when changing something after a skip node
Issue -
State: closed - Opened by GerwinBosch 9 months ago
- 3 comments
#52 - Parser request: nix
Issue -
State: closed - Opened by IogaMaster 11 months ago
- 3 comments
#51 - Getting `Unhandled Runtime Error TypeError: Cannot read properties of undefined (reading 'deserialize')` issue in bun
Issue -
State: closed - Opened by gyanaranjans 11 months ago
- 5 comments
#50 - bug causing wrong token to be parsed in areas where they shouldn't be valid.
Issue -
State: closed - Opened by rvion about 1 year ago
- 1 comment
#49 - No types found for `@lezer/generator/rollup`
Issue -
State: closed - Opened by spaceemotion about 1 year ago
- 2 comments
#48 - Extend bundler support to Webpack and Vite using Unplugin
Issue -
State: closed - Opened by illright over 1 year ago
- 3 comments
#47 - what is the npm package of the lazer
Issue -
State: closed - Opened by jiangxiaoqiang over 1 year ago
- 1 comment
#46 - tree.children is undefined in @lezer/common
Issue -
State: closed - Opened by gtm-nayan over 1 year ago
- 5 comments
#45 - Add a printer package
Issue -
State: closed - Opened by deemp over 1 year ago
- 4 comments
#44 - generator runs out of memory on large grammar
Issue -
State: closed - Opened by nchen63 over 1 year ago
- 2 comments
#43 - Ignore/skipped tests?
Issue -
State: closed - Opened by vanillajonathan over 1 year ago
- 2 comments
#42 - Speeding up build parser
Issue -
State: closed - Opened by nchen63 over 1 year ago
- 3 comments
#41 - Generated `specialized` field is not compatible with typescript strict mode
Issue -
State: closed - Opened by berekuk over 1 year ago
- 4 comments
#40 - [generator] dist/rollup-plugin-lezer.cjs is missing in v1.4.1
Issue -
State: closed - Opened by hubgit over 1 year ago
- 2 comments
#39 - Types are broken when used with node16/nodenext
Issue -
State: closed - Opened by berekuk over 1 year ago
- 2 comments
#38 - Can't resolve 'process/browser'
Issue -
State: closed - Opened by Dazaer over 1 year ago
- 4 comments
#37 - How to get usable error messages?
Issue -
State: closed - Opened by unleashy almost 2 years ago
- 3 comments
#36 - Version 1.2.1 of @lezer/generator tokenizes differently
Issue -
State: closed - Opened by viktor-berglund-mw almost 2 years ago
- 2 comments
#35 - Token parsing behavior change in generator between 1.2.0 and 1.2.1
Issue -
State: closed - Opened by r3c almost 2 years ago
- 2 comments
#34 - Concise API for getting text of a node/token?
Issue -
State: closed - Opened by TedDriggs almost 2 years ago
- 2 comments
#33 - Large grammar causes error "Tokenizer tables too big to represent with 16-bit offsets"
Issue -
State: closed - Opened by nedgrady about 2 years ago
- 4 comments
#32 - PHP conflicts with Parcel watch mode: probably worth adding `require` to `KEYWORDS`
Issue -
State: closed - Opened by ashmind about 2 years ago
#31 - Potentially missing grammar for javascript tokenizer (Symbol.iterator)
Issue -
State: closed - Opened by kdog3682 over 2 years ago
- 1 comment
#30 - generator not importable from esm module
Issue -
State: closed - Opened by allain over 2 years ago
- 5 comments
#29 - Question: How to query "syntax tags" for a given Node/NodeType?
Issue -
State: closed - Opened by joshgoebel over 2 years ago
- 19 comments
#28 - Help contributing?
Issue -
State: closed - Opened by drwpow over 2 years ago
- 3 comments
#27 - Is it really this difficult?
Issue -
State: closed - Opened by pragdave over 2 years ago
- 1 comment
#26 - generator creates invalid code
Issue -
State: closed - Opened by BryanCrotaz over 2 years ago
- 5 comments
#25 - `firstChild` missing
Issue -
State: closed - Opened by joelburget almost 3 years ago
- 1 comment
#24 - Bug: parse fails when text contains many "skip" nodes
Issue -
State: closed - Opened by JuneKelly almost 3 years ago
- 13 comments
#23 - Sandbox is not working
Issue -
State: closed - Opened by b04505009 almost 3 years ago
- 2 comments
#22 - Grammar railroad diagram
Issue -
State: closed - Opened by mingodad almost 3 years ago
- 6 comments
#21 - Unterminated string handling regex can hang lezer-generator due to exponential backtracking
Issue -
State: closed - Opened by briangough almost 3 years ago
- 2 comments
#20 - Feature request: match quotes
Issue -
State: closed - Opened by pmg23 about 3 years ago
- 1 comment
#19 - Incorrect node nesting
Issue -
State: closed - Opened by unconed about 3 years ago
- 1 comment
#18 - Typings for Tree.resolve changed in `0.15.11`
Issue -
State: closed - Opened by paddyobrien about 3 years ago
- 1 comment
#17 - Proposal: a mixed-language interface accessible within ExternalTokenizer instances
Issue -
State: closed - Opened by ashtonsix about 3 years ago
- 4 comments
#16 - Inline terms not exported
Issue -
State: closed - Opened by ashtonsix about 3 years ago
- 2 comments
#15 - SyntaxError: No parse at x
Issue -
State: closed - Opened by milahu over 3 years ago
- 3 comments
#14 - Consider alternative approaches to forced reduction
Issue -
State: closed - Opened by marijnh over 3 years ago
- 1 comment
#13 - Infinite loop in recovery
Issue -
State: closed - Opened by backmask over 3 years ago
- 4 comments
#12 - Feature Request: Add Objective-C parser
Issue -
State: closed - Opened by bhamiltoncx over 3 years ago
- 1 comment
#11 - Generator could generate ts file
Issue -
State: closed - Opened by Nexucis over 3 years ago
- 2 comments
#10 - Query a syntax tree, – a la Tree-Sitter.
Issue -
State: closed - Opened by c4lliope over 3 years ago
- 2 comments
#9 - Generating lezer grammar from tree-sitter grammar?
Issue -
State: open - Opened by ubolonton over 5 years ago
- 2 comments
#8 - Consider making node names exports rather than strings
Issue -
State: closed - Opened by marijnh over 4 years ago
- 6 comments
#7 - Does Lezer support (or plan to support) local variables?
Issue -
State: closed - Opened by jasonhan-vassar about 4 years ago
- 3 comments
#6 - Running lezer-generator on a complex grammar results in an error "Goto table too large"
Issue -
State: open - Opened by poeschko about 4 years ago
- 6 comments
#5 - Profile and optimize
Issue -
State: closed - Opened by marijnh over 5 years ago
- 1 comment
#4 - Extending a predefined grammar.
Issue -
State: open - Opened by s0kil about 4 years ago
- 1 comment
#3 - Consider supporting a 'compress' action on stacks
Issue -
State: closed - Opened by marijnh about 4 years ago
- 1 comment
#2 - Rollup/yarn 2 plugin import error
Issue -
State: closed - Opened by jeeger about 4 years ago
- 5 comments
#1 - Consider using a monorepo
Issue -
State: closed - Opened by Timmmm over 3 years ago
- 1 comment