Closed Bug 1054285 Opened 11 years ago Closed 10 years ago

Revert disabling SSL verification in npm configuration of development VM

Categories

(developer.mozilla.org Graveyard :: General, defect)

Product:
developer.mozilla.org Graveyard
Component:
General
Platform:
All
Other
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jezdez, Unassigned)

References

Details

(Whiteboard: [specification][type:change])

What feature should be changed? Please provide the URL of the feature if possible. ================================================================================== This was done in https://github.com/mozilla/kuma/commit/4d2969992bb55a05f26d93b540bb8c7a06a0bf82 to work around an issue with an old version of npm that wasn't able to successfully verify the SSL cert of the NPM registry. https://github.com/npm/npm/issues/4379 has the details Also https://github.com/mozilla/kuma/issues/1831 shows some feedback from one of our contributors. What problems would this solve? =============================== Now that we're running a newer version of npm in the dev VM we can revert this deactivated SSL verification during development. Who would use this? =================== Developers and contributors What would users see? ===================== n/a What would users do? What would happen as a result? =================================================== n/a Is there anything else we should know? ======================================
Blocks: 1165924
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.