search

zurb / foundation-apps

The first front-end framework created for developing fully responsive web apps.
http://foundation.zurb.com/apps
MIT License
1.58k stars 216 forks source link

Error installing foundation-cli on Windows #203

Closed jsmreese closed 9 years ago

jsmreese commented 9 years ago

I see this error when I run npm install -g foundation-cli on Windows (Windows 7 64bit):

image

gakimball commented 9 years ago

@fhassan2014 The template project uses Bundler to install the right version of Sass for you. Run bundle install and then try compiling again.

The next version of the CLI won't require Ruby or Bundler, thankfully :)

fhassan2014 commented 9 years ago

@gakimball here I tested again. looks fine your test build:

image

gakimball commented 9 years ago

@fhassan2014 Ah that's fantastic :) Thanks again for trying it out.

gakimball commented 9 years ago

@fhassan2014 You can just run gulp if you have it installed globally. The way the watch and build commands work changed slightly in the new CLI, although the functionality is the same.

foundation-apps watch is identical to npm start which is identical to gulp.

fhassan2014 commented 9 years ago

Hi @gakimball getting these errors while watch command. Any suggestion would be appreciated. Need to test one project to see how Foundation for apps works. Thanks.

image

gakimball commented 9 years ago

@fhassan2014 Try just running gulp inside your project folder instead, since that's what the watch command is running. (If you don't have Gulp: npm install -g gulp)

The watch command will make more sense once all three of the Foundation frameworks use the CLI, and then watch becomes a shorthand for "run whatever this project needs to run".

soumak77 commented 9 years ago

@gakimball Just as curiosity, what are those three frameworks? Foundation for Apps, Foundation for Sites, and ...?

gakimball commented 9 years ago

@soumak77 Ink is the third one, which is being rebranded as Foundation for Emails when v2.0 comes out in a few months. Unifying the branding partially represents our push to share more code, styles, and best practices between the three frameworks.

soumak77 commented 9 years ago

@gakimball Oh ok, yeah I new about Ink and the rebranding to Foundation for Emails, but didn't realize there was a need for a CLI for that framework. I thought it was just templates you copied and manually injected whatever content you needed into the provided areas. I haven't used F4E yet (which may be clear by my last statement), though that is definitely something I want to get started with as my company emails need some much loving care.

fhassan2014 commented 9 years ago

@gakimball now getting this final page. Not sure it suppose to be like this. result

and got this error before building project: image

Before all this I had this Warning Engin: foundation-cli@1.0.4: wanted: <"node":">=0.10.33"> <current: 0.10.32, npm: 1.4.28

I hope you'll find any solution on this. I also tried running gulp and gave me this screen: image

gakimball commented 9 years ago

@fhassan2014 The second error EADDRINUSE means you already have a server for another Apps project running, or at least you have something else running on port 8080. Close out your other build process, run gulp again, and then it should work.

fhassan2014 commented 9 years ago

@gakimball Thanks! it's fine, the only thing lift is browser is looking these missing files. any thoughts.

result

gakimball commented 9 years ago

@fhassan2014 It looks like the Sass isn't compiling to CSS; that's why there's a "Not Found" error in the console, for css/app.css. Are you still getting the same gulp-ruby-sass error in your other screenshots?

fhassan2014 commented 9 years ago

@gakimball Yes. Any solution.

gakimball commented 9 years ago

@fhassan2014 I just noticed you're running a pre-release build of JRuby, so I think that's the issue. The error is being generated by the Sass executable, meaning it's a Ruby error, not a JavaScript one. You might need to switch to a stable version of JRuby, or file an issue with their team.

gakimball commented 9 years ago

This is a somewhat older issue, so I'm going to close it out. The original issue filed has been fixed, and version 1.1 of the CLI, which we published last month, greatly improves the stability and error-handling of the project creation process.

If y'alls have any more issues with the CLI in the future, do let us know :)

narration-sd commented 9 years ago

Thanks, Geoff.

On Apr 20, 2015, at 11:21, Geoff Kimball notifications@github.com wrote:

This is a somewhat older issue, so I'm going to close it out. The original issue filed has been fixed, and version 1.1 of the CLI, which we published last month, greatly improves the stability and error-handling of the project creation process.

If y'alls have any more issues with the CLI in the future, do let us know :)

— Reply to this email directly or view it on GitHub.