Foundation-sites: ENOENT: no such file or directory, rename ansistyles

[holisticnetworking]

How to reproduce this bug:

1. Attempt to install Zurb Foundation CLI by issuing the following command:
   npm install --global foundation-cli
2. Error

What should happen:

The Foundation CLI should install without errors

What happened instead:

Got the following error message:
npm ERR! code ENOENT

npm ERR! errno -2

npm ERR! syscall rename

npm ERR! enoent ENOENT: no such file or directory, rename '/Users/tomb/npm-global/lib/node_modules/foundation-cli/node_modules/npm/node_modules/ansistyles' -> '/Users/tomb/npm-global/lib/node_modules/foundation-cli/node_modules/npm/node_modules/.ansistyles.DELETE'

npm ERR! enoent This is related to npm not being able to find a file.

npm ERR! enoent

Browser(s) and Device(s) tested on:

Mac El Capitan

Foundation Version(s) you are using:

Latest stable build

Test case link:

Here is a complete log file from my installation:
https://gist.github.com/holisticnetworking/efb6e065cedb43d6467e8e5b5f1de148

[ncoden]

I'm working on this.

[ncoden]

This only happens where we try to install foundation-cli twice. But it doesn't seem related to foundation-cli. See: https://github.com/npm/npm/issues/17444

Try:

npm uninstall --global foundation-cli
npm install --global foundation-cli

[holisticnetworking]

That, along with rebuilding node-sass, seems to be working.

[liamse]

It is happen after I try to install rimraf package.
To solve the problem, I rename node_modules to node_modules_2 and run npm install. this download all packages again and I uninstall one module (any module you want, and you can install it back). This solves the problem for me. After check that everything is work fine, I remove my corrupted node_modules_2 folder.

[ncoden]

@liamse You can simply uninstall then reinstall foundation-cli.

[liamse]

Thanks @ncoden but I don't have foundation-cli at all.
I think this is NPM issue, and it happens when we want to install more than one packages with same dependencies, I think dependencies make conflict and NPM think that it has a file that does not exist at all. Uninstalling any package, clear something (that I don't know exactly what) in NPM and this solve issue, and we then can install any other package with NPM.

[webuxr]

@liamse Have you tried npm dedupe (https://docs.npmjs.com/cli/dedupe)? I’m not sure how this might affect your package.json but it may be worth a test.

[jomesili]

Using npm dedupe solved this issue for me

[mzunigau]

not working:
Unistalling / reinstalling
installing node-sass , gulp-sass
npm dedupe
reinstalling nodejs
so sad, i think i'm gonna quit foundation cli...

[ncoden]

@mzunigau This is not a problem with Foundation CLI.

Can you try deleting the global foundation-cli folder ? Use npm ls -gl foundation-cli to find where it is installed.

$ npm ls -gl foundation-cli

│ /Users/ncoden/.nvm/versions/node/v8.9.1/lib
│
└── [email protected]
    Command-line interface for the Foundation family of frameworks.
    git+https://github.com/zurb/foundation-cli.git
    https://foundation.zurb.com

[henryhobhouse]

We have a similar problem with our internal CLI at the moment. First install perfect. Second time the same error is popping up. Folder has to be deleted before reinstall/update can happy. Let me know if you find a solution as all options found so far haven't seem to fix the issue. I should add that the issue seems to only be on Linux.

[torican]

Uninstall/reinstall worked for me.... Ubuntu 16.04.3 LTS

[DanielRuf]

along with rebuilding node-sass

If this is the case try npm rebuild node-sass --force

[DanielRuf]

Should we reopen this one here or create a new issue?

[DanielRuf]

$ npm install --global foundation-cli
npm WARN deprecated [email protected]: ...psst! Your project can stop working at any moment because its dependencies can change. Prevent this by migrating to Yarn: https://bower.io/blog/2017/how-to-migrate-away-from-bower/
C:\Users\Daniel\AppData\Roaming\npm\foundation -> C:\Users\Daniel\AppData\Roaming\npm\node_modules\foundation-cli\bin\foundation.js
+ [email protected]
updated 2 packages in 48.586s

$ npm install --global foundation-cli
npm WARN deprecated [email protected]: ...psst! Your project can stop working at any moment because its dependencies can change. Prevent this by migrating to Yarn: https://bower.io/blog/2017/how-to-migrate-away-from-bower/
C:\Users\Daniel\AppData\Roaming\npm\foundation -> C:\Users\Daniel\AppData\Roaming\npm\node_modules\foundation-cli\bin\foundation.js
+ [email protected]
updated 1 package in 11.122s


$ npm install --global foundation-cli
npm WARN deprecated [email protected]: ...psst! Your project can stop working at any moment because its dependencies can change. Prevent this by migrating to Yarn: https://bower.io/blog/2017/how-to-migrate-away-from-bower/
C:\Users\Daniel\AppData\Roaming\npm\foundation -> C:\Users\Daniel\AppData\Roaming\npm\node_modules\foundation-cli\bin\foundation.js
+ [email protected]
updated 1 package in 13.129s

$ node --version
v8.8.1

$ npm --version
5.3.0

Not reproducible (anymore).

Please provide more info about your environment.

[Anke]

Getting this message trying to download custom build (only forms, changed grid's max-width to 60 as well as colors) from your download page:
ENOENT: no such file or directory, stat '/tmp/tmp.6.5.1.c4d2f0efbeb98b1c44ef947b272a60f9.zip'

Edit: No error message as long as I don't change the right hand side default values

[DanielRuf]

Hi @Anke,

please see https://github.com/foundation/node-foundation-customizer/pull/13 and https://github.com/foundation/foundation-sites/issues/11795 and also https://github.com/foundation/foundation-sites/issues/11826