Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
I have updated to the latest npm v8.3.1 and it is showing me an error while using the command "npm outdated -g --depth=0". See the image; https://imgur.com/a/5fMZlye. It was fine on v8.3.0. What is the solution?
Expected Behavior
It should return the outdated packages after a successful run. But it is giving error.
Steps To Reproduce
- In this environment...
- With this config...
- Run '...'
- See error...
I am using Windows 10 (Enterprise - Latest Version). I have the latest node and npm installed at the moment.
Environment
- npm:
- Node.js:
- OS Name:
- System Model Name:
- npm config:
; copy and paste output from `npm config ls` here
; "user" config from C:\Users\Bilal.npmrc
registry = "http://registry.npmjs.org/"
; node bin location = C:\Program Files\nodejs\node.exe
; cwd = C:\Users\Bilal
; HOME = C:\Users\Bilal
; Run npm config ls -l to show all defaults.
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
I have updated to the latest npm v8.3.1 and it is showing me an error while using the command "npm outdated -g --depth=0". See the image; https://imgur.com/a/5fMZlye. It was fine on v8.3.0. What is the solution?
Expected Behavior
It should return the outdated packages after a successful run. But it is giving error.
Steps To Reproduce
I am using Windows 10 (Enterprise - Latest Version). I have the latest node and npm installed at the moment.
Environment
; copy and paste output from `npm config ls` here; "user" config from C:\Users\Bilal.npmrc
registry = "http://registry.npmjs.org/"
; node bin location = C:\Program Files\nodejs\node.exe
; cwd = C:\Users\Bilal
; HOME = C:\Users\Bilal
; Run
npm config ls -lto show all defaults.