Menu icon Foundation

Designer

I am using Foundation 5. And Apps.

My Posts

No Content

My Comments

Robert North commented on Robert North's post over 4 years

My ui-srefs had "/"'s in them.

The error in this case is a result of the uri being wrong.

Robert North commented on Robert North's post over 4 years

I just wanted to follow this up, because I would like to get my system configured properly to take advantage of the CLI.

Geoff said "If you can't get the installer working, you can also install manually. This will also help you figure out which step in the install process is going wrong. The instructions are on the readme for the template stack."

What do I know now that the manual installation works fine?

I've just tried:

foundation-apps new postmanual
cd postmanual
foundation-apps watch

Which returns:
```Error: Cannot find module './bower_components/foundation-apps/bin/gulp-dynamic-routing'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (/Users/Mercury/apps/postmanual/gulpfile.js:20:22)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)

npm ERR! [email protected] start: gulp
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is most likely a problem with the foundation-apps-template package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! gulp
npm ERR! You can get their info via:
npm ERR! npm owner ls foundation-apps-template
npm ERR! There is likely additional logging output above.
npm ERR! System Darwin 14.0.0
npm ERR! command "node" "/usr/local/bin/npm" "start"
npm ERR! cwd /Users/Mercury/apps/postmanual
npm ERR! node -v v0.10.35
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /Users/Mercury/apps/postmanual/npm-debug.log
npm ERR! not ok code 0
```

Geoff you also mentoned "However, you might still run into trouble if your Node install is configured in such a way that you need admin privileges to install software."

I've been trying to find out if this is the case - I went through the node installation process again installing a the package from node.js - is there a better way to go about this or way I can check?

Robert North commented on Robert North's post over 4 years

Oh man it is so much to wrap my head around. I didn't realise node was doing this sort of thing. I feel so stupid where have I been. You said it right somewhere that we've been designing like its 2007. So many new things to take it right now.

Robert North commented on Robert North's post over 4 years

My bad. I just added this to gulp.task('copy'... in the apps gulpfile.js

'./client/assets/img/*.*'

Robert North commented on Robert North's post over 4 years

I was trying every variation of running with and without sudo, to my feeble knowledge. To be honest after a day I gave up, very sad, but bruce my cat cheered me up.

Following this manual installation on githup you linked it works perfectly! Wish I found that sooner.

If there were a way to detect in CLI all that you said it would be great. As a newcomer to this it was really overwhelming and hard to debug. The instructions casually suggest if you're having troubles with commands try Sudo etc. I also learned (since i'm on mac) that the Ruby I was using by default may have been broken. I ended up installing some 2nd rbenv version. I just felt like a dog chasing his tail.

Well, thanks for that link for the readme - it helped a lot.

Posts Followed

No Content

Following

    No Content

Followers

My Posts

No Content

My Comments

You commented on Robert North's post over 4 years

My ui-srefs had "/"'s in them.

The error in this case is a result of the uri being wrong.

You commented on Robert North's post over 4 years

I just wanted to follow this up, because I would like to get my system configured properly to take advantage of the CLI.

Geoff said "If you can't get the installer working, you can also install manually. This will also help you figure out which step in the install process is going wrong. The instructions are on the readme for the template stack."

What do I know now that the manual installation works fine?

I've just tried:

foundation-apps new postmanual
cd postmanual
foundation-apps watch

Which returns:
```Error: Cannot find module './bower_components/foundation-apps/bin/gulp-dynamic-routing'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (/Users/Mercury/apps/postmanual/gulpfile.js:20:22)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)

npm ERR! [email protected] start: gulp
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is most likely a problem with the foundation-apps-template package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! gulp
npm ERR! You can get their info via:
npm ERR! npm owner ls foundation-apps-template
npm ERR! There is likely additional logging output above.
npm ERR! System Darwin 14.0.0
npm ERR! command "node" "/usr/local/bin/npm" "start"
npm ERR! cwd /Users/Mercury/apps/postmanual
npm ERR! node -v v0.10.35
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /Users/Mercury/apps/postmanual/npm-debug.log
npm ERR! not ok code 0
```

Geoff you also mentoned "However, you might still run into trouble if your Node install is configured in such a way that you need admin privileges to install software."

I've been trying to find out if this is the case - I went through the node installation process again installing a the package from node.js - is there a better way to go about this or way I can check?

You commented on Robert North's post over 4 years

Oh man it is so much to wrap my head around. I didn't realise node was doing this sort of thing. I feel so stupid where have I been. You said it right somewhere that we've been designing like its 2007. So many new things to take it right now.

You commented on Robert North's post over 4 years

My bad. I just added this to gulp.task('copy'... in the apps gulpfile.js

'./client/assets/img/*.*'

You commented on Robert North's post over 4 years

I was trying every variation of running with and without sudo, to my feeble knowledge. To be honest after a day I gave up, very sad, but bruce my cat cheered me up.

Following this manual installation on githup you linked it works perfectly! Wish I found that sooner.

If there were a way to detect in CLI all that you said it would be great. As a newcomer to this it was really overwhelming and hard to debug. The instructions casually suggest if you're having troubles with commands try Sudo etc. I also learned (since i'm on mac) that the Ruby I was using by default may have been broken. I ended up installing some 2nd rbenv version. I just felt like a dog chasing his tail.

Well, thanks for that link for the readme - it helped a lot.

Posts Followed

No Content

Following

  • No Content

Followers

  • No Content