felixrieseberg/npm-windows-upgrade issues and pull requests

#179 - Can't execute npm-windows_update

Issue - State: open - Opened by zebrassimo over 3 years ago

#178 - Cannot install latest version on Windows

Issue - State: open - Opened by gabrielw007 over 3 years ago - 1 comment

#177 - while enter npm start for runt a react app it shows error like this

Issue - State: open - Opened by sabari74 over 3 years ago

#176 - failed to upgrade npm

Issue - State: open - Opened by purveshshende2 over 3 years ago

#175 - npm ERR! code EINTEGRITY

Issue - State: open - Opened by Monster3425 over 3 years ago

#174 - npm install express --save Error

Issue - State: open - Opened by FionaObed-fiona over 3 years ago

#173 - "Scripts cannot be executed on this system." on pwsh 7 if process scope is not Unrestricted

Issue - State: open - Opened by Fred-Vatin over 3 years ago

#172 - Fix typo in emoji name in README.md

Pull Request - State: closed - Opened by apeteri over 3 years ago

#171 - ⬆️ Bump hosted-git-info from 2.7.1 to 2.8.9

Pull Request - State: open - Opened by dependabot[bot] over 3 years ago
Labels: dependencies

#170 - Revert ":arrow_up: Bump lodash from 4.17.11 to 4.17.21"

Pull Request - State: open - Opened by jacky88866 over 3 years ago

#169 - ⬆️ Bump lodash from 4.17.11 to 4.17.21

Pull Request - State: open - Opened by dependabot[bot] over 3 years ago
Labels: dependencies

#168 - You wanted to install npm 7.6.1, but the installed version is 6.14.11.

Issue - State: closed - Opened by era5mx almost 4 years ago - 2 comments

#166 - Cannot find module 'npm-windows-upgrade.js'

Issue - State: open - Opened by wayaway-jtm almost 4 years ago

#165 - npx create-react-app => Error EINTEGRITY

Issue - State: open - Opened by ajcanelhas about 4 years ago

#164 - Error to upgrade: from 6.14.8 to the latest

Issue - State: open - Opened by John-saint about 4 years ago

#163 - Error: Npm start

Issue - State: open - Opened by kanwar002 over 4 years ago

#161 - Failed to upgrade from 6.14.6 to 6.14.8

Issue - State: open - Opened by arfaWong over 4 years ago - 2 comments

#160 - npm ERR! cb.apply is not a function While trying to Update the Npm the Windows way.

Issue - State: open - Opened by utsabshrestha over 4 years ago - 1 comment

#159 - ⬆️ Bump lodash from 4.17.11 to 4.17.19

Pull Request - State: closed - Opened by dependabot[bot] over 4 years ago - 1 comment
Labels: dependencies

#158 - Can't update problem (even for admin)

Issue - State: open - Opened by goxr3plus over 4 years ago - 2 comments

#157 - npm install

Issue - State: open - Opened by Samumancio almost 5 years ago

#156 - ⬆️ Bump acorn from 6.0.4 to 6.4.1

Pull Request - State: open - Opened by dependabot[bot] almost 5 years ago
Labels: dependencies

#155 - expo start not opening project

Issue - State: closed - Opened by saadheikh about 5 years ago

#153 - I got this error at the time of run command "ng serve --open".

Issue - State: closed - Opened by Ankur3444 about 5 years ago - 1 comment

#152 - Add console.log with installed npm version

Pull Request - State: closed - Opened by sergeysedoy97 about 5 years ago - 1 comment

#151 - ⬆️ Bump eslint-utils from 1.3.1 to 1.4.3

Pull Request - State: open - Opened by dependabot[bot] about 5 years ago
Labels: dependencies

#150 - Error: spawn powershell.exe ENOENT

Issue - State: closed - Opened by MahmoudMabrok over 5 years ago - 4 comments

#149 - Scope specified more than once (powershell)

Issue - State: open - Opened by mflux over 5 years ago

#148 - No upgrade when running against node install via nvm-windows

Issue - State: open - Opened by TonyApuzzo over 5 years ago - 2 comments

#147 - Couldnt push app to heroku after installing the dependency

Issue - State: open - Opened by CaesarBourne over 5 years ago - 2 comments

#146 - npm ERR! code EINTEGRITY integrity checksum failed

Issue - State: open - Opened by PAnilReddy over 5 years ago - 3 comments

#145 - Readme should mention proxy

Issue - State: open - Opened by holgerl over 5 years ago

#144 - failed to upgrade

Issue - State: open - Opened by a-wip0 over 5 years ago - 1 comment

#143 - Upgrading from 6.4.1 to 6.9.0 hangs

Issue - State: open - Opened by sandy0201 almost 6 years ago

#142 - Make non-admin error message less specific

Pull Request - State: closed - Opened by cookieguru almost 6 years ago - 3 comments

#141 - Fixed link in "logUpgradeFailure" to refer to #fix-an-attempted-upgrade URL

Pull Request - State: closed - Opened by willediger almost 6 years ago - 1 comment

#140 - Failed to upgrade from 6.4.1 to 6.8.0

Issue - State: open - Opened by sgaspari almost 6 years ago - 4 comments

#139 - Upgrade appears successful but error reported

Issue - State: open - Opened by Lekinho almost 6 years ago - 1 comment

#138 - Unexpected Identifier in Upgrader.Js

Issue - State: closed - Opened by rolfea about 6 years ago - 14 comments

#137 - Cannot find module '../src/compatible'

Issue - State: closed - Opened by bogacg about 6 years ago - 1 comment

#136 - Upgraded but npm -v still returns old

Issue - State: open - Opened by TS22082 about 6 years ago - 1 comment

#135 - Fails to install due to unpublished NPM requirements..

Issue - State: open - Opened by ghost over 6 years ago

#134 - Failed to upgrade

Issue - State: open - Opened by carpben over 6 years ago - 6 comments

#133 - Setting ExecutionPolicy to "Unrestriced" is an unnecessary risk

Issue - State: open - Opened by Ztarbox over 6 years ago - 5 comments

#132 - You wanted to install npm 6.4.1, but the installed version is 5.6.0.

Issue - State: open - Opened by hengsoheak over 6 years ago - 1 comment

#131 - Non-exact versions cause an installation error

Issue - State: open - Opened by akdor1154 over 6 years ago

#130 - Failed to upgrade from 5.6.0 to 6.4.1

Issue - State: open - Opened by daghb over 6 years ago

#129 - Failed upgrade 6.2.0 to 6.4.0 on Node 10.9.0 that was installed with NVM on Windows 7

Issue - State: open - Opened by fipda over 6 years ago

#128 - Can't update 6.1 to 6.2

Issue - State: open - Opened by iamcrunchy over 6 years ago - 1 comment

#127 - Error: Cannot find module 'cli-cursor'

Issue - State: closed - Opened by PGorshkov over 6 years ago - 1 comment

#126 - Unhandled promise rejection In non-english systems

Issue - State: closed - Opened by jidma over 6 years ago - 3 comments

#125 - http://aka.ms/fix-npm-upgrade link is broken

Issue - State: closed - Opened by 2-5 almost 7 years ago - 3 comments

#124 - Can't update from NPM 5.6.0 to 5.7.

Issue - State: open - Opened by itpcc almost 7 years ago - 8 comments

#123 - --no-execution-policy-check gets ignored

Issue - State: closed - Opened by Krizzzn almost 7 years ago - 1 comment

#122 - Some Host Script Error 800A03F6

Issue - State: closed - Opened by mdsManu almost 7 years ago - 1 comment

#121 - Upgrade failure on Win10 pro

Issue - State: open - Opened by TracyGJG about 7 years ago - 4 comments

#120 - npm install

Issue - State: closed - Opened by MMSharif about 7 years ago - 1 comment

#119 - [Feature Request] Upgrade npx

Issue - State: open - Opened by michaeljota over 7 years ago

#118 - Buffer.alloc is not a function

Issue - State: closed - Opened by epicfaace over 7 years ago - 1 comment

#117 - Upgrading the Visual Studio 2017 default npm fails: automation?

Issue - State: open - Opened by natalie-o-perret over 7 years ago - 4 comments

#116 - Failed to update NPM 5.3 to 5.4

Issue - State: open - Opened by muj-beg over 7 years ago - 5 comments
Labels: more-information-needed

#115 - Can npm-windows-upgrade add a registry option ? it might be nice for China user :)

Issue - State: open - Opened by Jaycexx over 7 years ago

#114 - npm-windows-upgrade to npm 5.2.0 does not install npx

Issue - State: open - Opened by cchamberlain over 7 years ago

#113 - npm ERR! code EINTEGRITY integrity checksum failed when using sha1

Issue - State: closed - Opened by davidpodhola over 7 years ago - 21 comments

#112 - Added final cleanup step to check chocolatey

Pull Request - State: closed - Opened by ntregillus over 7 years ago - 2 comments

#111 - Third time the charm (newest node msi + npm-windows-upgrade failing)

Issue - State: closed - Opened by ntregillus over 7 years ago - 3 comments

#110 - failure while attempting to update

Issue - State: closed - Opened by ntregillus over 7 years ago - 3 comments

#109 - failing to upgrade, even after uninstall and reinstall of nodejs

Issue - State: closed - Opened by ntregillus over 7 years ago - 4 comments

#108 - Error installing upgrade (Use of const in strict mode)

Issue - State: closed - Opened by brian-k over 7 years ago - 2 comments

#107 - Failing due to i18n "OS Version"

Issue - State: closed - Opened by CedricLevasseur almost 8 years ago - 5 comments

#106 - Npm not getting installed on Window 10

Issue - State: closed - Opened by akshaygpt almost 8 years ago

#105 - New to coding error with npm

Issue - State: closed - Opened by williamjjlee almost 8 years ago

#104 - It's not working with Windows 7

Issue - State: closed - Opened by RHMason almost 8 years ago - 5 comments

#103 - npm-windows-upgrade

Issue - State: closed - Opened by cscaushik about 8 years ago - 1 comment

#102 - Allow an execution policy of "Bypass"

Pull Request - State: closed - Opened by olivierdagenais about 8 years ago - 2 comments

#101 - Node v7.1.0 Compatibility Issue?

Issue - State: closed - Opened by jwuliger about 8 years ago - 8 comments
Labels: upstream

#100 - "Upgrading npm ... /" is blinking

Issue - State: open - Opened by igor-toporet about 8 years ago - 1 comment
Labels: bug, help wanted

#99 - Document installation do latest version

Issue - State: closed - Opened by otjutt about 8 years ago - 1 comment

#98 - Couldn't upgarde

Issue - State: closed - Opened by shiva-p17 over 8 years ago

#97 - Fix option name in error log

Pull Request - State: closed - Opened by piotr-cz over 8 years ago - 1 comment

#96 - Syntax Error: Unexpected token R

Issue - State: closed - Opened by cawoodm over 8 years ago - 2 comments

#95 - Safer way to allow execution policy

Issue - State: closed - Opened by Eibwen over 8 years ago - 1 comment

#94 - Weird, unexpected output.

Issue - State: closed - Opened by 462960 over 8 years ago - 2 comments

#93 - arrow keys do not respond

Issue - State: closed - Opened by GaryB432 over 8 years ago - 5 comments
Labels: bug

#92 - How do I turn off all the

Issue - State: closed - Opened by nickarino over 8 years ago

#91 - Fix typo in help

Pull Request - State: closed - Opened by bdukes over 8 years ago - 1 comment

#90 - Select latest version by defauly, not the highest one

Issue - State: open - Opened by gligoran over 8 years ago

#89 - Codesign ps1 Script

Pull Request - State: closed - Opened by felixrieseberg over 8 years ago

#88 - If your domain policy has script executionPolicy set to remoteSigned, how can you use npm-windows-upgrade?

Issue - State: closed - Opened by mcking65 over 8 years ago - 7 comments

#87 - Extracting find-npm.js to it's own module

Issue - State: closed - Opened by LinusU over 8 years ago - 1 comment

#86 - Limited up to 3.10.6 npm version

Issue - State: closed - Opened by 462960 over 8 years ago - 1 comment

#84 - Removed npm when trying to upgrade, no error messages

Issue - State: closed - Opened by xargi over 8 years ago - 2 comments

#83 - Error installing npm-windows-upgrade

Issue - State: closed - Opened by stoberman37 over 8 years ago - 13 comments

#75 - Installation hangs with 'Upgrading...'

Issue - State: closed - Opened by erinev over 8 years ago - 1 comment

#72 - Install latest NPM with no prompts option?

Issue - State: closed - Opened by ghost over 8 years ago - 3 comments

#66 - Error: Could not determine npm version

Issue - State: closed - Opened by ccrowhurstram almost 9 years ago - 8 comments

#41 - Error Launching npm-windows-upgrade

Issue - State: closed - Opened by gregoryagu over 9 years ago - 24 comments

GitHub / felixrieseberg/npm-windows-upgrade issues and pull requests