Open Luna-Klatzer opened 2 years ago
I think the problem is in your npm config file
Also facing this issue preventing versions from being undeprecated, appears to be another regression of https://github.com/npm/cli/pull/3484
This only happens on Windows. The command executes as expected on macOS 12 and Alpine Linux
npm config
; "builtin" config from C:\Users\wopia\AppData\Roaming\npm\node_modules\npm\npmrc
prefix = "C:\\Users\\wopia\\AppData\\Roaming\\npm"
; "user" config from C:\Users\wopia\.npmrc
//registry.npmjs.org/:_authToken = (protected)
; node bin location = C:\Program Files\nodejs\node.exe
; node version = v18.5.0
; npm local prefix = C:\GitHub\wopian\kitsujs
; npm version = 8.17.0
; cwd = C:\GitHub\wopian\kitsujs
; HOME = C:\Users\wopia
; Run `npm config ls -l` to show all defaults.
Any update or workaround, facing the same issue?
Any update or workaround, facing the same issue?
Fixed it, on created the react app with npx create then ran upgrade and
npm audit fix --force
as suggested when run successfully but with compiled and got comments when implemented/run. this breaks it. and got the above error. the thing it fixed is by using the command
npm install react@latest
followed by
npm install react-dom@latest
npm install react-scripts@latest
This is still an issue. Confirmed to be on Windows; works fine on my Mac.
I realized this only occurs while using Powershell. Switching to Command Prompt solved the problem.
Try double-quoting the argument (two double quotes inside of two single quotes), like this: npm deprecate package@1.0.0 '""'
I have faced the same problem and it still exists. I found that this issue occurs in PowerShell, but it does not occur in Git Bash.
This problem could be resolved by adding the package-lock.json
, runnpm install
and then try npm ci
I have error but i don't know how i can solve it:
PS C:\Users\kolme\Downloads\API_REST_1> npm star
npm ERR! code EUSAGE
npm ERR!
npm ERR! Mark your favorite packages
npm ERR!
npm ERR! Usage:
npm ERR! npm star [
npm ERR! A complete log of this run can be found in: C:\Users\kolme\AppData\Local\npm-cache_logs\2024-06-25T15_18_56_495Z-debug-0.log
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
When trying to un-deprecate certain versions of my
@kipper/base
module, there is an error saying there is a usage error, despite following the guidelines on the docs page:My command:
The output:
Full verbose log:
Expected Behavior
The command should execute properly and un-deprecate the package.
Steps To Reproduce
npm login
npm deprecate PACKAGE@VERSION ""
Environment
prefix = "C:\Users\Luna\AppData\Roaming\npm"
; "global" config from C:\Users\Luna\AppData\Roaming\npm\etc\npmrc
; python = "C:\Users\Luna\.windows-build-tools\python27\python.exe" ; overridden by user
; "user" config from C:\Users\Luna.npmrc
@kipper:registry = "https://registry.npmjs.org/" //registry.npmjs.org/:_authToken = (protected) python = "C:\Users\Luna\.windows-build-tools\python27\python.exe" scope = "@kipper"
; node bin location = C:\Program Files\nodejs\node.exe ; node version = v16.13.0 ; npm local prefix = C:\Users\Luna ; npm version = 8.8.0 ; cwd = C:\Users\Luna ; HOME = C:\Users\Luna ; Run
npm config ls -l
to show all defaults.