npm install cloudinary command fail

Elliot Cho

December 26, 2022 04:04

Hi, when I tried npm install cloudinary I get an error stating that 'node' is not recognized as an internal or external command. I know this may sound like a common issue that can be resolved by setting a node environment variable in my path, but I already have that variable set. I literally triple checked. Additionally, all previous node and npm commands have been working. The only time npm install has been failing has been when I try to run npm install cloudinary and npm install multer-storage-cloudinary. I'm running the command in the top level of the project directory where the package.json is as well. I'll leave the actual error printed out below.

$ npm install cloudinary

npm ERR! code 1
npm ERR! path C:\Users\User\Documents\ProjectDirectory\node_modules\core-js
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c node -e "try{require('./postinstall')}catch(e){}"
npm ERR! 'node' is not recognized as an internal or external command,
npm ERR! operable program or batch file.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\User\AppData\Local\npm-cache\_logs\2022-12-26T03_52_20_923Z-debug-0.log

0

• 

  Tamara Yulevich

  December 26, 2022 13:50

  Hi Eliot, 

  This issue doesn't seem to be related to Cloudinary but to your `User variables`, please take a look at this Stackoverflow post: 

  https://stackoverflow.com/questions/23412938/node-is-not-recognized-as-an-internal-or-an-external-command-operable-program

  Please tell me if you have any further questions, 

  -Tamara

  0
• 

  Elliot Cho

  December 26, 2022 18:18

  So cloudinary installed through npm today but im not sure if it is a consistent solution. I deleted my package-lock.json and ran npm install, which I've done before but it didn't work the first time. I'm not sure why it suddenly worked today but just thought I would leave this update and post here in case anyone else has the same issue. Also Tamara, the stackoverflow post talks about adding a node environment variable into my path, which I said I already properly did and didn't fix the issue.

  0
• 

  Tamara Yulevich

  December 27, 2022 14:02

  Hi Eliot, 

  Node is not recognized means either node is not installed correctly or path is not set.

  So install Node JS on your machine from https://nodejs.org/en/download/

  Check out this guide on how to install Node properly while setting path - https://blog.teamtreehouse.com/install-node-js-npm-windows

  Thanks, 

  Tamara

  0

Post is closed for comments.