Breaking changes: scoping the npm package and dropping Node.js < 10 support (RFC for MDN Data 3.0)
Open
Nobody has claimed this yet.
idle
- Dominant language
- JavaScript
- Stars
- 787
- Forks
- 216
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 6
Description
Summary
MDN Data should make a couple of breaking changes:
- move the package into the
@mdnscope on npm (i.e., renamemdn-datato@mdn/data) - drop support for Node.js < 10.
See https://github.com/mdn/browser-compat-data/issues/6640 for details.
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 reading the linked browser-compat-data issue for the rationale and scope of the proposed breaking changes. Then identify the package and release metadata affected by the npm rename and Node.js support change; done means the scoped package and minimum runtime policy are consistently defined without leaving the old package name or unsupported runtime guidance behind.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100