yo famous - ERROR - Githubissues

e4chess commented 10 years ago

After I input: yo famous

The terminal gives me this error below. Btw - I have Node.js & npm pkg installed. Not to mention there were zero ERRORs after: $ npm install -g yo grunt-cli bower generator-famous

How do I fix?

Thanks in advance!

Error: EACCES, permission denied '/Users/e4chess/.config/configstore/insight-yo.yml' You don't have access to this file.

at Object.fs.openSync (fs.js:427:18)
at Object.fs.writeFileSync (fs.js:966:15)
at Object.create.all.set (/usr/local/lib/node_modules/yo/node_modules/insight/node_modules/configstore/configstore.js:61:8)
at Object.Configstore (/usr/local/lib/node_modules/yo/node_modules/insight/node_modules/configstore/configstore.js:24:11)
at new Insight (/usr/local/lib/node_modules/yo/node_modules/insight/lib/insight.js:22:34)
at Object.<anonymous> (/usr/local/lib/node_modules/yo/bin/yo:26:15)
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)

e4chess commented 10 years ago

It appears that my User has no permissions to use [yo] let alone [yo famous]. So I tried using this piece of code to update my permissions: sudo chown myusername /Users/myusername/.config/configstore/update-notifier-yo.ymlchown

Still getting ERROR response..

Then this: sudo chown -R myusername ~/.config

AND Viola! It WORKED - Yo is installed and running version 1.1.2.

Minus this hiccup after running yo famous....

 _-----_
|       |
|--(o)--|   .--------------------------.

---------´ | Welcome to Yeoman, | ( _´U_ ) | ladies and gentlemen! | /_A_\ '__' | ~ | '._.'__ ´ |° ´ Y

You're using the fantastic Famo.us generator. [?] Your project name: (newProject) fs.js:427 return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode); ^ Error: EACCES, permission denied '/Users/e4chess/newProject/.yo-rc.json' at Object.fs.openSync (fs.js:427:18) at Object.fs.writeFileSync (fs.js:966:15) at Storage.forceSave (/usr/local/lib/node_modules/generator-famous/node_modules/yeoman-generator/lib/util/storage.js:71:6) at Storage.bound (/usr/local/lib/node_modules/generator-famous/node_modules/lodash/dist/lodash.js:729:21) at delayed as _onTimeout at Timer.listOnTimeout as ontimeout

I'm unsure what the issue is here... is it JSON?

e4chess commented 10 years ago

https://www.npmjs.org/package/generator-famous

Be Aware of .yo-rc.json

When this generator scaffolds out a project it generates a .yo-rc.json file. This file allows yo to run again in the same directory without prompting you for information. This is particularly useful if you want to update your project to be based on the latest version of generator-famous. This can be a problem though, as yo searches up the file tree to check if there is a version of .yo-rc.json. So if you for example accidentally ran yo famous from a directory that was not empty, you might end up leaving the .yo-rc.json in the directory above where you would like to be. The result will be then when running yo in an empty directory afterwards your files will never end up in the folder you are expecting them to.

Ok. So I don't quite understand how to correct the .yo,-rc.json file mess...

MylesBorins commented 10 years ago

This is a very odd error indeed. Have you tried running the generator in a different directory?

What operating system are you on?

I would appear it is running into a problem actually writing to disk, so I am assuming .yo-rc.json is never even written

On Apr 29, 2014, at 3:18 AM, e4chess notifications@github.com wrote:

https://www.npmjs.org/package/generator-famous

Be Aware of .yo-rc.json

When this generator scaffolds out a project it generates a .yo-rc.json file. This file allows yo to run again in the same directory without prompting you for information. This is particularly useful if you want to update your project to be based on the latest version of generator-famous. This can be a problem though, as yo searches up the file tree to check if there is a version of .yo-rc.json. So if you for example accidentally ran yo famous from a directory that was not empty, you might end up leaving the .yo-rc.json in the directory above where you would like to be. The result will be then when running yo in an empty directory afterwards your files will never end up in the folder you are expecting them to.

Ok. So I don't quite understand how to correct the .yo,-rc.json file mess...

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

e4chess commented 10 years ago

Myles I tried using a different directory and it worked.....

Woot! It appears that everything installed correctly. Please run the command grunt serve to launch the development server. Most questions you have will be answered in the generated README.md

Bye from us! Chat soon.

        Addy Osmani
      Sindre Sorhus
    Brian Ford
 Eric Bidelman
          Paul Irish
 Mickael Daniel
      Pasca1 Hartig
  Stephen S.wchuk
Frederick R0s

But unfortunately I ran into another issue after inputing the last command: grunt serve

A valid Gruntfile could not be found. Please see the getting started guide for more information on how to configure grunt: http://gruntjs.com/getting-started Fatal error: Unable to find Gruntfile.

Current Grunt Version Below -- grunt-cli v0.1.13 grunt v0.4.4

Thanks again for your help!

MylesBorins commented 10 years ago

Try running npm install && bower install On Apr 29, 2014 11:36 AM, "e4chess" notifications@github.com wrote:

Myles I tried using a different directory and it worked.....

Woot! It appears that everything installed correctly. Please run the command grunt serve to launch the development server. Most questions you have will be answered in the generated README.md

Bye from us! Chat soon.
    Addy Osmani
  Sindre Sorhus
Brian Ford
Eric Bidelman Paul Irish Mickael Daniel Pasca1 Hartig Stephen S.wchuk Frederick R0s

But unfortunately I ran into another issue after inputing the last command: grunt serve

A valid Gruntfile could not be found. Please see the getting started guide for more information on how to configure grunt: http://gruntjs.com/getting-started Fatal error: Unable to find Gruntfile.

Current Grunt Version Below -- grunt-cli v0.1.13 grunt v0.4.4

Thanks again for your help!

— Reply to this email directly or view it on GitHubhttps://github.com/Famous/generator-famous/issues/24#issuecomment-41715183 .

e4chess commented 10 years ago

npm WARN package.json newProject@0.0.0 No repository field. npm WARN package.json newProject@0.0.0 No README data

MylesBorins commented 10 years ago

Did you run yo famous On Apr 29, 2014 11:39 AM, "e4chess" notifications@github.com wrote:

npm WARN package.json newProject@0.0.0 No repository field. npm WARN package.json newProject@0.0.0 No README data

— Reply to this email directly or view it on GitHubhttps://github.com/Famous/generator-famous/issues/24#issuecomment-41715548 .

e4chess commented 10 years ago

I did run: yo famous

Woot! It appears that everything installed correctly. Please run the command grunt serve to launch the development server. Most questions you have will be answered in the generated README.md

Then: grunt serve A valid Gruntfile could not be found. Please see the getting started guide for more information on how to configure grunt: http://gruntjs.com/getting-started Fatal error: Unable to find Gruntfile.

Hmmmm....

MylesBorins commented 10 years ago

Can you paste the output of ls ? On Apr 29, 2014 11:45 AM, "e4chess" notifications@github.com wrote:

I did run: yo famous

Woot! It appears that everything installed correctly. Please run the command grunt serve to launch the development server. Most questions you have will be answered in the generated README.md

Then: grunt serve A valid Gruntfile could not be found. Please see the getting started guide for more information on how to configure grunt: http://gruntjs.com/getting-started Fatal error: Unable to find Gruntfile.

Hmmmm....

— Reply to this email directly or view it on GitHubhttps://github.com/Famous/generator-famous/issues/24#issuecomment-41716252 .

e4chess commented 10 years ago

$ yo famous

 _-----_
|       |
|--(o)--|   .--------------------------.

---------´ | Welcome to Yeoman, | ( _´U_ ) | ladies and gentlemen! | /_A_\ '__' | ~ | '._.'__ ´ |° ´ Y

You're using the fantastic Famo.us generator. [?] Your project name: thread.it [?] Your project description: e.g. Seed project to get started with Famo.us [?] Would you mind telling me your username on Github? e4chess create README.md create app/index.html create app/content/images/famous_logo.png create app/styles/app.css create app/src/requireConfig.js create app/src/main.js create package.json create bower.json create Gruntfile.js create .editorconfig create .bowerrc create .eslintrc create .jscsrc create .gitignore create .travis.yml create grunt/aliases.js create grunt/eslint.js create grunt/jscs.js create grunt/watch.js create grunt/connect.js create grunt/clean.js create grunt/bower.js create grunt/rev.js create grunt/processhtml.js create grunt/useminPrepare.js create grunt/usemin.js create grunt/htmlmin.js create grunt/copy.js create grunt/requirejs.js

I'm all done. Running bower install & npm install for you to install the required dependencies. If this fails, try running the command yourself.

almond#0.2.9 app/lib/almond

requirejs#2.1.11 app/lib/requirejs

famous#0.1.2 app/lib/famous

grunt-rev@0.1.0 node_modules/grunt-rev

grunt-contrib-clean@0.5.0 node_modules/grunt-contrib-clean └── rimraf@2.2.6

time-grunt@0.3.1 node_modules/time-grunt ├── date-time@0.1.1 ├── pretty-ms@0.1.0 ├── text-table@0.2.0 ├── hooker@0.2.3 └── chalk@0.4.0 (ansi-styles@1.0.0, has-color@0.1.7, strip-ansi@0.1.1)

famous-metrics@0.0.9 node_modules/famous-metrics ├── osenv@0.0.3 ├── mixpanel@0.0.19 └── rc@0.3.5 (deep-extend@0.2.8, ini@1.1.0, minimist@0.0.8)

grunt-contrib-concat@0.4.0 node_modules/grunt-contrib-concat └── chalk@0.4.0 (has-color@0.1.7, ansi-styles@1.0.0, strip-ansi@0.1.1)

grunt-contrib-htmlmin@0.2.0 node_modules/grunt-contrib-htmlmin ├── each-async@0.1.2 ├── pretty-bytes@0.1.0 ├── html-minifier@0.5.6 └── chalk@0.4.0 (has-color@0.1.7, ansi-styles@1.0.0, strip-ansi@0.1.1)

grunt-contrib-cssmin@0.9.0 node_modules/grunt-contrib-cssmin ├── chalk@0.4.0 (has-color@0.1.7, ansi-styles@1.0.0, strip-ansi@0.1.1) ├── clean-css@2.1.8 (commander@2.1.0) └── maxmin@0.1.0 (pretty-bytes@0.1.0, gzip-size@0.1.1)

grunt-usemin@2.1.1 node_modules/grunt-usemin ├── debug@0.7.4 └── lodash@1.0.1

grunt-contrib-uglify@0.4.0 node_modules/grunt-contrib-uglify ├── chalk@0.4.0 (has-color@0.1.7, ansi-styles@1.0.0, strip-ansi@0.1.1) ├── maxmin@0.1.0 (pretty-bytes@0.1.0, gzip-size@0.1.1) └── uglify-js@2.4.13 (uglify-to-browserify@1.0.2, async@0.2.10, optimist@0.3.7, source-map@0.1.33)

grunt-contrib-requirejs@0.4.4 node_modules/grunt-contrib-requirejs └── requirejs@2.1.11

grunt-contrib-watch@0.6.1 node_modules/grunt-contrib-watch ├── async@0.2.10 ├── tiny-lr-fork@0.0.5 (debug@0.7.4, faye-websocket@0.4.4, noptify@0.0.3, qs@0.5.6) ├── lodash@2.4.1 └── gaze@0.5.1 (globule@0.1.0)

grunt-jscs-checker@0.4.1 node_modules/grunt-jscs-checker ├── vow@0.4.3 ├── hooker@0.2.3 ├── lodash.assign@2.4.1 (lodash._objecttypes@2.4.1, lodash.keys@2.4.1, lodash._basecreatecallback@2.4.1) └── jscs@1.3.0 (strip-json-comments@0.1.1, colors@0.6.0-1, vow@0.3.9, minimatch@0.2.12, commander@1.2.0, esprima@1.0.3, xmlbuilder@1.1.2, vow-fs@0.2.3, glob@3.2.7)

grunt@0.4.4 node_modules/grunt ├── which@1.0.5 ├── dateformat@1.0.2-1.2.3 ├── eventemitter2@0.4.13 ├── getobject@0.1.0 ├── rimraf@2.2.6 ├── colors@0.6.2 ├── grunt-legacy-util@0.1.2 ├── async@0.1.22 ├── nopt@1.0.10 (abbrev@1.0.5) ├── exit@0.1.2 ├── hooker@0.2.3 ├── minimatch@0.2.14 (sigmund@1.0.0, lru-cache@2.5.0) ├── glob@3.1.21 (inherits@1.0.0, graceful-fs@1.2.3) ├── lodash@0.9.2 ├── coffee-script@1.3.3 ├── underscore.string@2.2.1 ├── iconv-lite@0.2.11 ├── js-yaml@2.0.5 (argparse@0.1.15, esprima@1.0.4) └── findup-sync@0.1.3 (glob@3.2.9, lodash@2.4.1)

load-grunt-config@0.8.0 node_modules/load-grunt-config ├── async@0.2.10 ├── glob@3.2.9 (inherits@2.0.1, minimatch@0.2.14) ├── js-yaml@3.0.2 (argparse@0.1.15, esprima@1.0.4) ├── lodash-node@2.4.1 └── load-grunt-tasks@0.3.0 (globule@0.2.0, findup-sync@0.1.3)

grunt-eslint@0.4.0 node_modules/grunt-eslint ├── chalk@0.4.0 (has-color@0.1.7, ansi-styles@1.0.0, strip-ansi@0.1.1) └── eslint@0.5.1 (strip-json-comments@0.1.1, estraverse@1.3.2, text-table@0.2.0, escope@1.0.1, optionator@0.3.0, doctrine@0.5.1, cssauron-esprima@0.0.1, glob@3.2.9, esprima@1.1.1, js-yaml@3.0.2)

grunt-processhtml@0.3.3 node_modules/grunt-processhtml └── htmlprocessor@0.1.2 (lodash@2.4.1)

grunt-contrib-connect@0.7.1 node_modules/grunt-contrib-connect ├── connect-livereload@0.3.2 ├── open@0.0.4 ├── async@0.2.10 ├── portscanner@0.2.2 (async@0.1.15) └── connect@2.13.1 (uid2@0.0.3, methods@0.1.0, debug@0.8.1, cookie-signature@1.0.1, pause@0.0.1, bytes@0.2.1, buffer-crc32@0.2.1, raw-body@1.1.3, qs@0.6.6, fresh@0.2.0, batch@0.5.0, cookie@0.1.0, compressible@1.0.0, negotiator@0.3.0, send@0.1.4, multiparty@2.2.0)

bower@1.3.3 node_modules/bower ├── is-root@0.1.0 ├── junk@0.3.0 ├── stringify-object@0.2.0 ├── which@1.0.5 ├── abbrev@1.0.5 ├── chmodr@0.1.0 ├── osenv@0.0.3 ├── opn@0.1.1 ├── archy@0.0.2 ├── graceful-fs@2.0.3 ├── lockfile@0.4.2 ├── rimraf@2.2.6 ├── bower-endpoint-parser@0.2.1 ├── bower-logger@0.2.2 ├── lru-cache@2.5.0 ├── nopt@2.2.1 ├── retry@0.6.0 ├── chalk@0.4.0 (has-color@0.1.7, ansi-styles@1.0.0, strip-ansi@0.1.1) ├── mkdirp@0.3.5 ├── tmp@0.0.23 ├── q@1.0.1 ├── request-progress@0.3.1 (throttleit@0.0.2) ├── bower-json@0.4.0 (deep-extend@0.2.8, intersect@0.0.3) ├── shell-quote@1.4.1 (array-filter@0.0.1, array-reduce@0.0.0, array-map@0.0.0, jsonify@0.0.0) ├── semver@2.2.1 ├── fstream@0.1.25 (inherits@2.0.1) ├── p-throttler@0.0.1 (q@0.9.7) ├── promptly@0.2.0 (read@1.0.5) ├── fstream-ignore@0.0.7 (inherits@2.0.1, minimatch@0.2.14) ├── tar@0.1.19 (inherits@2.0.1, block-stream@0.0.7) ├── glob@3.2.9 (inherits@2.0.1, minimatch@0.2.14) ├── decompress-zip@0.0.6 (mkpath@0.1.0, touch@0.0.2, readable-stream@1.1.13-1, binary@0.3.0) ├── request@2.34.0 (json-stringify-safe@5.0.0, qs@0.6.6, forever-agent@0.5.2, tunnel-agent@0.3.0, aws-sign2@0.5.0, oauth-sign@0.3.0, node-uuid@1.4.1, mime@1.2.11, form-data@0.1.2, tough-cookie@0.12.1, http-signature@0.10.0, hawk@1.0.0) ├── cardinal@0.4.4 (ansicolors@0.2.1, redeyed@0.4.4) ├── inquirer@0.4.1 (readline2@0.1.0, mute-stream@0.0.4, through@2.3.4, async@0.2.10, lodash@2.4.1, cli-color@0.2.3) ├── handlebars@1.3.0 (optimist@0.3.7, uglify-js@2.3.6) ├── bower-config@0.5.0 (optimist@0.6.1, mout@0.6.0) ├── update-notifier@0.1.8 (semver@2.1.0, request@2.27.0, configstore@0.2.3) ├── mout@0.9.1 ├── insight@0.3.1 (object-assign@0.1.2, async@0.2.10, lodash.debounce@2.4.1, request@2.27.0, configstore@0.2.3) └── bower-registry-client@0.2.0 (request-replay@0.2.0, lru-cache@2.3.1, async@0.2.10, request@2.27.0, bower-config@0.4.5)

grunt-bower-requirejs@0.10.0 node_modules/grunt-bower-requirejs ├── bower@1.3.3 (junk@0.3.0, is-root@0.1.0, stringify-object@0.2.0, which@1.0.5, abbrev@1.0.5, chmodr@0.1.0, osenv@0.0.3, opn@0.1.1, archy@0.0.2, graceful-fs@2.0.3, lockfile@0.4.2, rimraf@2.2.6, bower-logger@0.2.2, lru-cache@2.5.0, bower-endpoint-parser@0.2.1, nopt@2.2.1, retry@0.6.0, chalk@0.4.0, mkdirp@0.3.5, tmp@0.0.23, q@1.0.1, request-progress@0.3.1, bower-json@0.4.0, semver@2.2.1, shell-quote@1.4.1, fstream@0.1.25, p-throttler@0.0.1, promptly@0.2.0, fstream-ignore@0.0.7, glob@3.2.9, tar@0.1.19, decompress-zip@0.0.6, request@2.34.0, update-notifier@0.1.8, inquirer@0.4.1, handlebars@1.3.0, cardinal@0.4.4, insight@0.3.1, bower-config@0.5.0, mout@0.9.1, bower-registry-client@0.2.0) └── bower-requirejs@0.10.3 (slash@0.1.1, object-assign@0.1.2, nopt@2.1.2, sudo-block@0.3.0, chalk@0.4.0, glob@3.2.9, file-utils@0.2.0, lodash@2.4.1, requirejs@2.1.11, update-notifier@0.1.8)

Woot! It appears that everything installed correctly. Please run the command grunt serve to launch the development server. Most questions you have will be answered in the generated README.md

$ grunt serve A valid Gruntfile could not be found. Please see the getting started guide for more information on how to configure grunt: http://gruntjs.com/getting-started Fatal error: Unable to find Gruntfile.

e4chess commented 10 years ago

ls newproject node_modules package.json threadit

MylesBorins commented 10 years ago

Try cd ING into new project On Apr 29, 2014 11:57 AM, "e4chess" notifications@github.com wrote:

ls newproject node_modules package.json threadit

— Reply to this email directly or view it on GitHubhttps://github.com/Famous/generator-famous/issues/24#issuecomment-41717683 .

MylesBorins commented 10 years ago

If the folder is not empty it will make a new directory for you On Apr 29, 2014 12:10 PM, "Myles Borins" myles@famo.us wrote:

Try cd ING into new project On Apr 29, 2014 11:57 AM, "e4chess" notifications@github.com wrote:

ls newproject node_modules package.json threadit

— Reply to this email directly or view it on GitHubhttps://github.com/Famous/generator-famous/issues/24#issuecomment-41717683 .

e4chess commented 10 years ago

Ok. We have movement!

cd newProject

$ grunt serve Running "serve" task

Running "clean:server" (clean) task

Running "processhtml:dev" (processhtml) task File ".tmp/index.html" created.

Running "connect:livereload" (connect) task Started connect web server on http://localhost:1337

Running "watch" task Waiting...

This launched a new window to open up in my chrome browser displaying the famo.us logo - seems to be frozen though....

MylesBorins commented 10 years ago

That is exactly what is expected after install! On Apr 29, 2014 12:17 PM, "e4chess" notifications@github.com wrote:

Ok. We have movement!

cd newProject

$ grunt serve Running "serve" task

Running "clean:server" (clean) task

Running "processhtml:dev" (processhtml) task File ".tmp/index.html" created.

Running "connect:livereload" (connect) task Started connect web server on http://localhost:1337

Running "watch" task Waiting...

This launched a new window to open up in my chrome browser displaying the famo.us logo - seems to be frozen though....

— Reply to this email directly or view it on GitHubhttps://github.com/Famous/generator-famous/issues/24#issuecomment-41719884 .

e4chess commented 10 years ago

Perfect! Thank you!

MylesBorins commented 10 years ago

Awesome!

Could you close this issue? Messaging from phone here On Apr 29, 2014 12:18 PM, "e4chess" notifications@github.com wrote:

Perfect! Thank you!

— Reply to this email directly or view it on GitHubhttps://github.com/Famous/generator-famous/issues/24#issuecomment-41720060 .

e4chess commented 10 years ago

Muchas Gracias Senor Myles! Closed!

FamousArchives / generator-famous

yo famous - ERROR #24