Closed
Bug 1940268
Opened 2 months ago
Closed 2 months ago
Add a linter to ensure that names are not specified in non-published package.json files
Categories
(Developer Infrastructure :: Developer Environment Integration, task, P3)
Developer Infrastructure
Developer Environment Integration
Tracking
(firefox136 fixed)
RESOLVED
FIXED
136 Branch
Tracking | Status | |
---|---|---|
firefox136 | --- | fixed |
People
(Reporter: standard8, Assigned: standard8)
Details
Attachments
(1 file)
For places where we're using a package.json
file for dependencies, but not for publishing, we do not need to specify a package name in the package.json
file. Having a name may cause confusion as to if the package is published or not. Hence, we want to enforce having no name specified, unless it is a published package.
Writing a linter do this seems the best way for now. In future we could potentially use a custom ESLint rule, however that requires an update to ESLint v9 (bug 1872685), and a switch to their JSON parser implementation.
Assignee | ||
Comment 1•2 months ago
|
||
Pushed by mbanner@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/48c5cb88ab08
Add a linter for names in node package.json files. r=linter-reviewers,ahal
Status: NEW → RESOLVED
Closed: 2 months ago
status-firefox136:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 136 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•