# los errores de:
* dirscan
* noauthorize
*
en windows 10, se arrgelan asegurnadose de usar npm 5.3.0
otro manera es dando acceso comple to(full) a todas las cuentas que tenga el sistema
respecto de la carpeta en cuestion
# Error: somethig wrong with npx Command failed
npm config get cache --parseable
A bit more on that:
When nodejs is installed, the installation folder (eg: C:\Program Files\nodejs) is added to the system %PATH% environment variable.
However, your npm installation folder's bin directory %APPDATA%\bin is added to your user's %PATH% environment variable (since %APPDATAT% is essentially just %USERPROFILE%\AppData\Roaming).
Now here's the part where it breaks: in Windows, to get the final %PATH% value, the user's variable is appended to the system variable, which means that the nodejs installation folder comes before the npm bin folder, whiiiiiich means that the installed np[mx] will always be given preference over the one installed via npm install --global.
## Repación
I've personally fixed it by removing %PROGRAMFILES%\nodejs from my system path, and adding it to my user path after the %APPDATA%\npm entry.
# Error: ENOENT
E:\_lanoosferasync\w_desarrollo\client\node_modules\npm\node_modules\ansistyles
npm ERR! code ENOENT
npm ERR! errno -4058
npm ERR! syscall rename
ENOENT: no such file or directory, rename 'E:\_lanoosferasync\w_desarrollo\client\node_modules\npm\node_modules\ansistyles' -> 'E:\_lanoosferasync\w_desarrollo\client\node_modules\npm\node_modules\.ansistyles.DELETE'
npm ERR! enoent This is related to npm not being able to find a file.
## Repación
lo reparé con ```npm dedupe```
https://docs.npmjs.com/cli/dedupe
pueden consultar para ams opciones:
https://github.com/zurb/foundation-sites/issues/10826