felixrieseberg/npm-windows-upgrade

Automate "Cleaning" of an attempted upgrade

Open

#69 opened on Apr 2, 2016

View on GitHub
 (0 comments) (1 reaction) (0 assignees)JavaScript (145 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (2,509 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

@robertbaker wrote a great summary of what's required after someone attempted to upgrade npm with npm install npm or npm upgrade npm. We should offer an automation of the cleanup steps, probably using PowerShell, executed from the script npm-windows-upgrade --fix-attempted-upgrade.

The steps:

Uninstall nodejs, not repair!, UNINSTALL.
Go into %programfiles%\nodejs and delete the entire folder.
Delete %appdata%\npm and %appdata%\npm-cache
Edit your PATH and remove everything that references npm (either program files or appdata).

At this point you should have a blank slate. No node packages, no node in your path, nothing.

So then install the latest node from nodejs.org.

Then in powershell as an admin run npm i -g npm-windows-upgrade
then run npm-windows-upgrade
then update to latest npm.

Contributor guide

Research direction
Write a PowerShell script that automates the cleanup steps: uninstall Node.js, delete the folder %programfiles%\nodejs, delete %appdata%\npm and %appdata%\npm cache, edit PATH to remove npm references, then install the latest Node.js from nodejs.org, and finally run npm i g npm windows upgrade && npm windows upgrade. Test the script on a Windows machine.
Tech stack
nodejsshell
Domain
developer experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
PowerShellnpm
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65