Closed
Bug 1726413
Opened 4 years ago
Closed 4 years ago
Use mach npm install rather than plain npm when updating node_modules
Categories
(Developer Infrastructure :: Lint and Formatting, task, P3)
Developer Infrastructure
Lint and Formatting
Tracking
(firefox93 fixed)
RESOLVED
FIXED
93 Branch
| Tracking | Status | |
|---|---|---|
| firefox93 | --- | fixed |
People
(Reporter: standard8, Assigned: standard8)
Details
Attachments
(1 file)
Now we have ./mach npm we should use that rather than plain npm when we update node_modules.
This will give us better package-lock.json output that matches the npm in use by the build system, rather than the npm that happens to be installed on the system of the person updating node_modules.
|
Assignee | |
Comment 1•4 years ago
|
||
Pushed by mbanner@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/6789b3c53f73
Use mach npm install rather than plain npm when updating node_modules. r=Mardak
|
||
Comment 3•4 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox93:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 93 Branch
|
||
Updated•3 years ago
|
Product: Firefox Build System → Developer Infrastructure
You need to log in
before you can comment on or make changes to this bug.
Description
•