Review & update Technical Priorities
Open
Nobody has claimed this yet.
next-10-agenda
- Dominant language
- No language data
- Stars
- 550
- Forks
- 31
- Avg merge
- 4h 27m
- Merged PRs (30d)
- 1
Description
Node's technical priorities is apparently co-owned by next-10 and the TSC, but it hasn't been updated in 2 years. We ask about this in the User survey (the 2026 one will go out soon).
For example, I think "Suitable types for end-users" is "done" and can be removed?
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 with doc/contributing/technical-priorities.md and the linked 2026 survey pull request. Review which priorities remain current, including whether “Suitable types for end-users” is complete, then update the document once the revised priorities are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100