Breaking changes: scoping the npm package and dropping Node.js < 10 support (RFC for MDN Data 3.0)

Open
#427 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, node.js
Domain
release

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.

Description

idle

Summary

MDN Data should make a couple of breaking changes:

  • move the package into the @mdn scope on npm (i.e., rename mdn-data to @mdn/data)
  • drop support for Node.js < 10.

See https://github.com/mdn/browser-compat-data/issues/6640 for details.

Dominant language
JavaScript
Stars
787
Forks
216
Avg merge
1d 5h
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mdn/data

All issues in mdn/data

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.