Any plans for a JavaScript parser?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- elixir, javascript
- Domain
- compilers
Research direction
The issue names no files, tests, or entry points. Start by reviewing the existing ESTree node definitions and JavaScript code generator in this Elixir repository to understand the expected AST shape. Done would require a concrete parser scope and an implementation that generates ASTs from JavaScript source.
Written by the indexing model from the issue text.
Description
I wouldn't know where to start but I'd be more than happy to help in implementing a JavaScript parser to generate AST's from source code.
- Dominant language
- Elixir
- Stars
- 104
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
phoenixframework/phoenix#6847 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
moderation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
beyond-all-reason/teiserver#1584 · 1 comment ·