Menu icon Foundation
Windows Path Foundations CLI

I followed the setup instructions. When I type foundation-apps new projectName I get:

'foundation-apps' is not recognized as an internal or external command,
operable program or batch file.

I'm not sure where foundation-cli is or how to add it to PATH.

foundation-apps

I followed the setup instructions. When I type foundation-apps new projectName I get:

'foundation-apps' is not recognized as an internal or external command,
operable program or batch file.

I'm not sure where foundation-cli is or how to add it to PATH.

Rafi Benkual almost 4 years ago

What folder did you run npm install -g foundation-cli bower gulp to?

There is a way to install manually also
download the zip
npm install
bower install
bundle

John Bocook almost 4 years ago

I ran it in the user root directory. I just tried in the project directory and had the same issue.

I ran through the install on another vm and here is the output that one received.

http://pastebin.com/KhLS8JPQ

John Bocook almost 4 years ago

I was able to follow the instructions on OSX, but for windows it just fails to work.

Martin Sweeny over 3 years ago

I'm having the problem

Martin Sweeny over 3 years ago

I'm on Windows 10, using npm install -g foundation-cli gives me no errors:

npm WARN engine foundation-cli@2.0.0: wanted: {"node":">=0.10.33"} (current: {"node":"0.10.30","npm":"1.4.21"})

npm WARN deprecated exec@0.1.4: deprecated in favor of builtin child_process.execFile
C:\Users\Martin\AppData\Roaming\npm\foundation -> C:\Users\Martin\AppData\Roaming\npm\node_modules\foundation-cli\bin\cli.js

foundation-cli@2.0.0 postinstall C:\Users\Martin\AppData\Roaming\npm\node_modules\foundation-cli
node lib/welcome.js

foundation-cli@2.0.0 C:\Users\Martin\AppData\Roaming\npm\node_modules\foundation-cli
├── is-root@1.0.0
├── exec@0.1.4
├── open@0.0.5
├── colors@1.1.2
├── async@0.9.2
├── nopt@3.0.6 (abbrev@1.0.7)
├── string-length@1.0.1 (strip-ansi@3.0.0)
├── multiline@1.0.2 (strip-indent@1.0.1)
├── which@1.2.0 (is-absolute@0.1.7)
├── semver@4.3.6
├── paint-by-number@1.0.0 (chalk@1.1.1)
├── rimraf@2.4.4 (glob@5.0.15)
├── inquirer@0.8.5 (ansi-regex@1.1.1, figures@1.4.0, cli-width@1.1.0, through@2.3.8, readline2@0.1.1, chalk@1.1.1, lodash@3.10.1, rx@2.5.3)
├── update-notifier@0.2.2 (is-npm@1.0.0, chalk@0.5.1, semver-diff@2.1.0, latest-version@1.0.1, configstore@0.3.2)
├── npm@2.14.13
└── bower@1.6.8

Then, when I run foundation-apps new whatever:

'foundation-apps' is not recognized as an internal or external command,
operable program or batch file.

Philip Cook over 3 years ago

In the final release version of Foundation 6 the command is just

foundation new

this provides an interactive selection of
1. Type of Project
2. Project Name
3. Framework

OK

James Stone over 3 years ago

I recently created a video that might help if you are working on a windows installation.

https://www.youtube.com/watch?v=JKywQK4NPdc

Did you install git prior to node? Are you able to run it from the same directory?

Gary Wenneker over 3 years ago

Strangly after updating to the new foundation my app isn't building anymore.
I hope there's an upgrade sequence??

<<<
[07:55:41] Using gulpfile C:_svn\CloudDB\3.0\app\gulpfile.js
[07:55:41] Starting 'build'...
[07:55:41] Starting 'clean'...
[07:55:42] 'clean' errored after 912 ms
[07:55:42] Error: EBUSY: resource busy or locked, rmdir 'C:_svn\CloudDB\3.0\app\build'
at Error (native)
[07:55:42] 'build' errored after 918 ms
[07:55:42] Error in plugin 'run-sequence'
Message:
An error occured in task 'clean'.
Error: foundation-apps-template@1.1.0 start: gulp
>>>

http://pastebin.com/0qxWCtTn