[BUG] npm view --json outputs illegal JSON for existing package but non-existent version #3184

Activity

1. rjgotten

   added

   Bugthing that needs fixingthing that needs fixing

   Needs Triageneeds review for next stepsneeds review for next steps

   Release 7.xwork is associated with a specific npm 7 releasework is associated with a specific npm 7 release

   on May 4, 2021
2. wraithgar

   added

   Priority 2secondary priority issuesecondary priority issue

   and removed

   Needs Triageneeds review for next stepsneeds review for next steps

   on May 12, 2021
3. varungandhi-src commented on Nov 8, 2021

   

   varungandhi-src

   on Nov 8, 2021

   More actions

   It looks like this problem isn't specific to the --json flag. Without the --json flag, as of npm 7.20.3, using npm view react@9999 will exit successfully instead of emitting an error and exiting with a non-zero exit code.
4. lukekarrys

   self-assigned this

   on May 11, 2024
5. lukekarrys commented on May 13, 2024

   

   lukekarrys

   on May 13, 2024

   Contributor

   More actions

   All of these cases now correctly set the exit code to 1 and show the relevant error. In --json mode that error is present in the json output.

   ❯ npm --version
   10.7.0
   
   ❯ npm view npm@11 --json
   npm error code E404
   npm error 404 No match found for version 11
   npm error 404
   npm error 404  'npm@11' is not in this registry.
   npm error 404
   npm error 404 Note that you can also install from a
   npm error 404 tarball, folder, http url, or git url.
   {
     "error": {
       "code": "E404",
       "summary": "No match found for version 11",
       "detail": "\n 'npm@11' is not in this registry.\n\nNote that you can also install from a\ntarball, folder, http url, or git url."
     }
   }
   
   npm error A complete log of this run can be found in: /Users/lukekarrys/.npm/_logs/2024-05-13T22_12_44_503Z-debug-0.log
   
   ❯ npm view npm@11 version --json
   npm error code E404
   npm error 404 No match found for version 11
   npm error 404
   npm error 404  'npm@11' is not in this registry.
   npm error 404
   npm error 404 Note that you can also install from a
   npm error 404 tarball, folder, http url, or git url.
   {
     "error": {
       "code": "E404",
       "summary": "No match found for version 11",
       "detail": "\n 'npm@11' is not in this registry.\n\nNote that you can also install from a\ntarball, folder, http url, or git url."
     }
   }
   
   npm error A complete log of this run can be found in: /Users/lukekarrys/.npm/_logs/2024-05-13T22_13_04_350Z-debug-0.log
   
   ❯ npm view npm@11
   npm error code E404
   npm error 404 No match found for version 11
   npm error 404
   npm error 404  'npm@11' is not in this registry.
   npm error 404
   npm error 404 Note that you can also install from a
   npm error 404 tarball, folder, http url, or git url.
   
   npm error A complete log of this run can be found in: /Users/lukekarrys/.npm/_logs/2024-05-13T22_13_19_311Z-debug-0.log
   
   ❯ npm view npm@11 version
   npm error code E404
   npm error 404 No match found for version 11
   npm error 404
   npm error 404  'npm@11' is not in this registry.
   npm error 404
   npm error 404 Note that you can also install from a
   npm error 404 tarball, folder, http url, or git url.
   
   npm error A complete log of this run can be found in: /Users/lukekarrys/.npm/_logs/2024-05-13T22_13_27_269Z-debug-0.log
6. lukekarrys

   closed this as completedon May 13, 2024