Remove babel config if node supports all ES6 features we need
Open
Nobody has claimed this yet.
chore
- Dominant language
- JavaScript
- Stars
- 1.9k
- Forks
- 51
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 1
Description
After we update minimum node version to v8 (#186), we should see if we can remove the babel config and just use ES6 features directly. This will simplify the build config while also removing our reliance on several dependencies.
Contributor guide
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
Start by locating the Babel configuration, build setup, and dependencies affected by the minimum Node v8 requirement. Check whether the required ES6 features run directly on Node v8; done means the Babel configuration and unnecessary dependencies are removed while the build remains functional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100