Closed Bug 1940283 Opened 1 year ago Closed 10 months ago

Add a linter to ensure that licenses included via the top-level package.json are acceptable

Categories

(Developer Infrastructure :: Lint and Formatting, task, P3)

Tracking

(firefox142 fixed)

RESOLVED FIXED
142 Branch
Tracking Status
firefox142 --- fixed

People

(Reporter: standard8, Assigned: standard8)

References

Details

Attachments

(2 files)

When we ship new node modules, or update our node modules we should be checking that the licenses are (still) acceptable. Generally I've been checking this when I've reviewed the addition of new modules, but I think it would be reasonable to have an automated check for which a linter which would mean we don't have to remember to do it, and we have the list already written.

Currently I'm looking at using license-checker-rseidelsohn, though a couple of packages it requires use a different license (which we haven't checked before) and are obsolete. So I'm going to see if we're able to get that package updated to not use those.

Pushed by mbanner@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/e9966efeec10 https://hg.mozilla.org/integration/autoland/rev/3a17ceb87e6f Only clear out eslint-plugin-mozilla's node_modules directory when running ESLint set-up. r=linter-reviewers,sylvestre https://github.com/mozilla-firefox/firefox/commit/f194594a1e33 https://hg.mozilla.org/integration/autoland/rev/8357f48fa211 Add a node-licenses linter to ensure that licenses included via the top-level and eslint-plugin-mozilla package.json files are acceptable. r=linter-reviewers,releng-reviewers,frontend-codestyle-reviewers,jcristau,ahal,mossop
Status: ASSIGNED → RESOLVED
Closed: 10 months ago
Resolution: --- → FIXED
Target Milestone: --- → 142 Branch
Regressions: 2038921
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: