Hi. I am having trouble using grunt in my projects. I am setting up an Mac osx computer with version 11.0.1.
The project files (local) are in principle correct, since I use it on another computer and it works fine there.
When trying to install grunt-cli globally I get this error:
npm ERR! code ENOENT
npm ERR! syscall lstat
npm ERR! path /Users/bertanicolau/.npm-packages
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, lstat '/Users/bertanicolau/.npm-packages'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/bertanicolau/.npm/_logs/2020-11-23T17_06_23_295Z-debug.log
The .npm-packages folder does not exist in this location, instead the .npm folder does exist, I don't know why it is looking for another.
I have been trying to solve this error for more than two days, the problem is that the local configuration does not work correctly, since I get the message ~ bash: grunt command not found when trying to initialize grunt with the grunt or grunt watch command
I've tried clearing the npm cache, I've also tried deleting the package-lock.json file but none of this seems to work.
Can it be a npm or node version bug?
$ npm -v && node -v
7.0.8
v15.2.1
Hi. I am having trouble using grunt in my projects. I am setting up an Mac osx computer with version 11.0.1.
The project files (local) are in principle correct, since I use it on another computer and it works fine there.
When trying to install grunt-cli globally I get this error:
The
.npm-packagesfolder does not exist in this location, instead the.npmfolder does exist, I don't know why it is looking for another.I have been trying to solve this error for more than two days, the problem is that the local configuration does not work correctly, since I get the message
~ bash: grunt command not foundwhen trying to initialize grunt with thegruntorgrunt watchcommandI've tried clearing the npm cache, I've also tried deleting the package-lock.json file but none of this seems to work.
Can it be a npm or node version bug?