error This is probably not a problem with npm There is likely additional logging output above

Question

In my project  I m using Angular6 for the frontend  Now what I m trying to do is deploy my project which is in remote server into the actual server  I m using npm run build -prod command to build the frontend first  But I can t build my project since the following error occurs again and again   npm ERR  code ELIFECYCLE npm ERR  errno 134 npm ERR  Trackit-Revamp 6 0 0 build   ng build --prod --build-optimizer --aot  npm ERR  Exit status 134 npm ERR  npm ERR  Failed at the Trackit-Revamp 6 0 0 build script  npm ERR  This is probably not a problem with npm  There is likely additional logging output above  npm ERR  A complete log of this run can be found in  npm ERR      C  Users Indrajith E AppData Roaming npm-cache  logs 2019-08-22T08 41 00 271Z-debug log   My error log in the C  Users Indrajith E AppData Roaming npm-cache  logs 2019-08-22T08 41 00 271Z-debug log file path contains the same error details mentioned above   How can I resolve this problem

User · Answer

Following steps solves my problem   Add  C  Windows System32   to your system path variables   Run npm eject    Run npm start   Run npm eject   and agian run  npm start  And it worked

User · Answer

Delete node module directory and run below in command line rm -rf node modules rm package-lock json yarn lock npm cache clear --force npm install  If still not working  try below npm install webpack --save

User · Answer

I m new with react    Well i had the same output   Starting the development server     events js 196       throw er     Unhandled  error  event          Error  ENOSPC  System limit for number of file watchers reached  watch   opt lampp htdocs react-tuto public      at FSWatcher  lt computed gt   internal fs watchers js 168 26      at Object watch  fs js 1351 34      at createFsWatchInstance   opt lampp htdocs react-tuto node modules chokidar lib nodefs-handler js 38 15      at setFsWatchListener   opt lampp htdocs react-tuto node modules chokidar lib nodefs-handler js 81 15      at FSWatcher NodeFsHandler  watchWithNodeFs   opt lampp htdocs react-tuto node modules chokidar lib nodefs-handler js 233 14      at FSWatcher NodeFsHandler  handleDir   opt lampp htdocs react-tuto node modules chokidar lib nodefs-handler js 429 19      at FSWatcher  lt anonymous gt    opt lampp htdocs react-tuto node modules chokidar lib nodefs-handler js 477 19      at FSWatcher  lt anonymous gt    opt lampp htdocs react-tuto node modules chokidar lib nodefs-handler js 482 16      at FSReqCallback oncomplete  fs js 165 5  Emitted  error  event on FSWatcher instance at      at FSWatcher  handleError   opt lampp htdocs react-tuto node modules chokidar index js 260 10      at createFsWatchInstance   opt lampp htdocs react-tuto node modules chokidar lib nodefs-handler js 40 5      at setFsWatchListener   opt lampp htdocs react-tuto node modules chokidar lib nodefs-handler js 81 15           lines matching original stack trace          at FSReqCallback oncomplete  fs js 165 5      errno  -28    syscall   watch     code   ENOSPC     path    opt lampp htdocs react-tuto public     filename    opt lampp htdocs react-tuto public    npm ERR  code ELIFECYCLE npm ERR  errno 1 npm ERR  react-tuto 0 1 0 start   react-scripts start  npm ERR  Exit status 1 npm ERR   npm ERR  Failed at the react-tuto 0 1 0 start script  npm ERR  This is probably not a problem with npm  There is likely additional logging output above   npm ERR  A complete log of this run can be found in  npm ERR       home paulo  npm  logs 2019-12-16T16 46 27 856Z-debug log   I just tried   sudo npm start   And it worked

User · Answer

Please delete package-lock json and clear npm cache with npm cache clear --force and delete whole node modules directory Finally install or update packages again with npm install   npm update You can also add any new packages with npm install  lt package-name gt  This fixed for me  Thanks and happy coding

User · Answer

Finally  I found a solution to this problem without reinstalling npm and I m posting it because in future it will help someone  Most of the time this error occurs javascript heap went out of the memory  As the error says itself this is not a problem with npm  Only we have to do is   instead of   npm  run build -prod   extend the javascript memory by following   node --max old space size 4096 node modules  angular cli bin ng build --prod

User · Answer

I already have the same problem   and I fix it using npm update  amp  npm cache clean --force

User · Answer

first delete the file  project   then rm -rf   Users Indrajith E AppData Roaming npm-cache logs 2019-08-22T08 41 00 271Z-debug log  this is the file log  which is showing error   recreate your project for example  - npx create-react-app hello world then cd hello world  then npm start   I was also having this same error but hopefully after spending 1 day on this error i have got this solution and it got started perfectly and i also hope this works for you guys also

User · Answer

Delete your package-lock json file and node modules folder   Then do npm cache clean  npm cache clean --force   do  npm install  again and run

User · Answer

Check if port you want to run your app is free  For me  it was the problem

User · Answer

For me  I was trying to install an old version of bcrypt which was not found in npm  I just edited package json and manually put the latest version and then ran npm install and it worked

User · Answer

I m on Ubuntu 18 04  I fixed this problem by increasing the inotify max user watches using this command   echo 65536   sudo tee -a  proc sys fs inotify max user watches

User · Answer

Novice mistake  Make sure your package json file is coded correctly  I had    start    index node js  instead of   start    node index js    17  Delete your package-lock json file and node modules folder  Then do npm cache clean  npm cache clean --force do  npm install

User · Answer

Delete node modules rm -r node modules  install packages again npm install

User · Answer

For me  the problem was in firebase json  the site name was incorrect

User · Answer

Deleting the package-lock json did it for me  I d suggest you not push package-lock json to your repo as I wasted hours trying to npm install with the package-lock json in the folder which gave me helluva errors

[angular] error: This is probably not a problem with npm. There is likely additional logging output above

Examples related to angular

Examples related to npm

Examples related to deployment

Examples related to build