Menu icon Foundation
Foundation new error "ENOENT: no such file or directory, uv_chdir"

If i try to install a new project via the foundation CLI i get the error "ENOENT: no such file or directory, uv_chdir". (see image). I can't solve why i get this error.

Setup:
Windows 10
Git, version 2.6.3
Node, version 5.1.0
Npm, version 3.3.12
Bower, version 1.6.8
Gulp, version 3.9.0

Foundation error

FoundationsitesWebsiteclierror

If i try to install a new project via the foundation CLI i get the error "ENOENT: no such file or directory, uv_chdir". (see image). I can't solve why i get this error.

Setup:
Windows 10
Git, version 2.6.3
Node, version 5.1.0
Npm, version 3.3.12
Bower, version 1.6.8
Gulp, version 3.9.0

Foundation error
Klevis Miho almost 4 years ago

The same error happened to me on my friends Windows 10 PC.

We didn't solve it but I think it is a problem with Node and Npm version.

Geoffroy about 2 years ago

Any update on this problem? I have exactly the same problem :(

 

Error: ENOENT: no such file or directory, uv_chdir
    at Error (native)
    at process.chdir (C:\Users\geoffroy.baylaender\AppData\Roaming\npm\node_modules\foundation-cli\node_modules\graceful-fs\polyfills.js:14:9)
    at process.chdir (C:\Users\geoffroy.baylaender\AppData\Roaming\npm\node_modules\foundation-cli\node_modules\bower\lib\node_modules\graceful-fs\polyfills.js:18:9)
    at process.chdir (C:\Users\geoffroy.baylaender\AppData\Roaming\npm\node_modules\foundation-cli\node_modules\npm\node_modules\graceful-fs\polyfills.js:18:9)
    at C:\Users\geoffroy.baylaender\AppData\Roaming\npm\node_modules\foundation-cli\lib\commands\new.js:88:15
    at ChildProcess.exithandler (child_process.js:189:7)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at maybeClose (internal/child_process.js:891:16)
    at Socket.<anonymous> (internal/child_process.js:342:11)

Caine Boelhouwer about 2 years ago

Nope sorry...