Use preferred paths or aliases to force ES6 compilation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 16
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Adjust default conversion graph for JS, but use preferred paths or aliases to force ES6 compilation
- [ ] For JS, should have full input graph, e.g. can uglify plain JS files,
but rely on "preferred paths" to ensure that it gets es5ified first (can
configure in default settings this way)
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.
Research direction
The issue names the default conversion graph and preferred paths or aliases, but no files or tests. Start by locating the graph configuration and JavaScript conversion handling; done should mean plain JavaScript remains supported while the configured preferred path applies ES5 compilation first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100