test es6
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 10/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- testing-qa
Research direction
The issue names no files, tests, entry points, or expected ES6 behavior. First inspect the nodequill repository to determine what ES6 compatibility or testing means here; the work is complete only once a specific expectation and verification method are defined.
Written by the indexing model from the issue text.
Description
i haven't tried anything in es6 yet
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from matthewbub/nodequill
-
Difficulty 2/5 1-3 hours Newbie friendliness 50/100
matthewbub/nodequill#1 ·
All issues in matthewbub/nodequill
Similar issues
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
solana-foundation/solana-com#2245 ·
Maintainers usually reply within 1 day
-
tech debt
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
TAMULib/fw-registry#543 ·
Maintainers usually reply within 1 day
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
FortAwesome/Font-Awesome#21688 ·