yeoman / yeoman.io Goto Github PK

Hello everyone,

When yeoman is compiling my sass, sometimes i got an error message in my terminal : Running "reload" task
Cannot call method 'send' of null Use --force to continue.

and after that, the reload function when saving my scss file doesn't work anymore.

Could anyone explain what i'm doing wrong please ?
Thanks in advance

Node version v0.8.7
Yeoman version 0.9.6
I'm running on a iMac mid 2011 on 10.7.5

See: https://github.com/sindresorhus/bower-components/blob/gh-pages/js/main.js#L99

And hide the table.

Try searching for dsgdhsdgs here: http://sindresorhus.com/bower-components/

yeoman/yeoman#1072

If everyone could share what they want added to their profile on the sub teams page it would be a great help.

• Little profile/about
• Area you maintain/contribute to
• Any generators or yeoman related projects you maintain

Any expansion on this also welcome 👍

Hi,

I have been thinking about using Yeoman to improve my workflow but I am not sure how to go about using it with current workflow.

Most of my web apps are built using Node and I place all my static files in a public folder to be served up using Express.js. I use nodemon to reload my node server after file changes and I make jQuery ajax calls to my server using REST.

I would like to add Yeoman into the mix but first attempts have left me a little lost!

I would like to build a generator that will allow Yeoman to simple watch the public folder, and some how get Yeoman server to start up my node server so that I can get all the great front end features that Yeoman offers, and still be able to run node on the same port so that my web app can make regular JSON ajax calls instead of JSONP.

Please can you point me in the right directions as to what I need to do, or whether this is even possible?

Keep up the good work :)

Jay

See: https://github.com/gruntjs/gruntjs.com/pull/79/files

// @ericduran if interested.

at the bottom of the page
🍶

First off, English is not my first language but I noticed some tiny things that I think could be corrected when I read through http://yeoman.io/packagemanager.html

"The easiest approach is to use a Bower package statically is to then just reference the package manually from a script tag:"

• I think the first "is" is not needed. So, it should be:
• "The easiest approach to use a Bower package statically is to (then) just reference the package manually from a script tag:"

"Bower is trying to solve the common problem, in an unopinionated way, and leave the opinions your build stack."

• "to" missing, I think this should be:
• "Bower is trying to solve the common problem, in an unopinionated way, and leave the opinions to your build stack."

Please, just disregard if I'm wrong.

David

After creating the Initializer generator the docs state:

Now, we can see that the initializer generator available to use if we output the list of available generators in this application:

$ yeoman init generator

Usage: yeoman generate GENERATOR [args] [options]
...

Please choose a generator below.

...

Initializer:
  initializer

What I actually see when I run yeoman init generator

$ yeoman init generator

Usage:
  yeoman init generator NAME [options]

Options:
  -h, --help  # Print generator's options and usage  
              # Default: false

Description:
    Stubs out a new generator at lib/generators. Pass the generator name as an argument.

Example:
    `yeoman generate generator Awesome`

    creates a standard awesome generator:
        lib/generators/awesome/
        lib/generators/awesome/index.js
        lib/generators/awesome/USAGE
        lib/generators/awesome/templates/

Actually running yeoman init initializer does execute the generator but I can't figure out any way to list its existence. yeoman init --help shows all of the built in generators but not Initializer

on packagemanager.html:

@hemanth could you look into how we can streamline our usage of /blog? Right now we don't have any build instructions available in the readme and there isn't a clear path for how others might build the blog portion of the site.

How would someone go about building it so that it could appear on /blog (in a compiled form, ready for consumption by end users?)

Cross-posting from yeoman/generator#337.

the github site doesnt have much visibility on the yeoman site.
let's fix that.

http://lab.hakim.se/forkit-js/

anyone wanna take a crack?

Repo: https://github.com/ericduran/yeoman-generator-list
URL: http://yeoman-plugin-list.herokuapp.com

Used for Generator Page (#62)

ANGER. Stop teasing! :)

https://npmjs.org/package/generator-flight

It mets the demands described at the bottom of the community-generators page, but isn't being displayed.

If I run yeoman init angular
Everything is fine I get the angular seed project setup.

But then if I want to add bootstrap and run yeoman install bootstrap

It removes all the files in the vendor folder including the angular.js files and just adds the bootstrap folder. And it does not update the index.html file not sure if it should.

I understood the install method lets you add packages to your project.

Following on from #34:

I have started work on re-factoring the site code to make better use of jekyll as well as making it easier to tweak and update the site in the future.

My plan is to have several different layouts in use for different pages of the site (at the moment there is one 'default' layout). One layout for documentation (with the sidebar) and a landing page layout for the homepage.

• Create layouts for docs and landing page
• Make landing page static (not based on wiki contents)
• Implement layouts for docs (with sidebar for navigation)

I'm happy to take up maintaining the website, if you have any ideas let me know 👍

The site nav doesn't use the current (or previous) Twitter logo :)

Now that there's a lot of generators out there it would be useful to have a list on the site with all of them fetched directly from the npm registry.

Should be easy to reuse the bits from the old grunt site or the bower component site to achieve this. Most of the code is already written. It's just about integrating it into the site.

Anyone up for it?

@tomlane @ericduran @zenorocha

/ping @ericduran

https://yeoman-plugin-list.herokuapp.com/ shows "Internal Server Error".

Trying to access the Yeoman website today has produced 404 errors for me since about 1pm.

Every time the command is run, it spits out the following error:

  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^
TypeError: path must be a string
    at Object.fs.openSync (fs.js:427:18)
    at Object.fs.readFileSync (fs.js:284:15)
    at yoyo.Base.rootGeneratorName (/usr/local/lib/node_modules/yo/node_modules/yeoman-generator/lib/base.js:533:24)
    at yoyo.Base._setStorage (/usr/local/lib/node_modules/yo/node_modules/yeoman-generator/lib/base.js:542:34)
    at yoyo.Base (/usr/local/lib/node_modules/yo/node_modules/yeoman-generator/lib/base.js:85:8)
    at new yoyo (/usr/local/lib/node_modules/yo/bin/yoyo.js:12:18)
    at Environment.create (/usr/local/lib/node_modules/yo/node_modules/yeoman-generator/lib/env.js:366:10)
    at Environment.run (/usr/local/lib/node_modules/yo/node_modules/yeoman-generator/lib/env.js:409:24)
    at init (/usr/local/lib/node_modules/yo/bin/yo:97:7)
    at pre (/usr/local/lib/node_modules/yo/bin/yo:109:3)

I have boiled it down to base.js line 533 being the culprit.

moved from yeoman/yeoman

Similar to #383 in yeoman/yeoman, it seems like the link to read more about usage statistics has gone MIA. The link is referenced after running yo generator:

==========================================================================
We're constantly looking for ways to make yo better! 
May we anonymously report usage statistics to improve the tool over time? 
More info: yeoman.io/insight.html & http://yeoman.io
==========================================================================

Hi, I' have some trouble installing yeoman on a cygwin installation, and pretty sure this used to work earlier.

I have installed node for windows and installed yeoman using npm install yeoman -g from cygwin. (v. 0.9.6)

Python is also installed under cygwin, but when I run yeoman -h it complains that it can't find python.

Does anyone have an idea on what could be wrong and what I can do to fix this? It seems like yeoman is running under cmd and not under sh for some reason?

me@-PC ~
$ which python
/usr/bin/python

me@-PC ~
$ which yeoman
/cygdrive/c/Users/me/AppData/Roaming/npm/yeoman

me@-PC ~
$ yeoman -h
cygwin warning:
  MS-DOS style path detected: C:\Users\me\AppData\Roaming\npm/node
  Preferred POSIX equivalent is: /cygdrive/c/Users/me/AppData/Roaming/npm/node
  CYGWIN environment variable option "nodosfilewarning" turns off this warning.
  Consult me user's guide for more details about POSIX paths:
    http://cygwin.com/cygwin-ug-net/using.html#using-pathnames
==========================================================================
We're constantly looking for ways to make yeoman better!
May we anonymously report usage statistics to improve me tool over time?
More info: yeoman.io/insight.html & http://yeoman.io
==========================================================================
[?] [Y/n]:  (Y) n
'python' is not recognized as an internal or external command,
operable program or batch file.


me@-PC ~
$

From the docs:

And now let’s change the generator to copy this template when invoked:

var util = require('util'),
    yeoman = require('../../../');

module.exports = Generator;

function Generator() {
  yeoman.generators.NamedBase.apply(this, arguments);
  // if your templates/ location differ, feel free to set it with sourceRoot()
}

util.inherits(Generator, yeoman.generatos.NamedBase);

Generator.prototype.copyInitializerFile = function() {
  this.copy('initializer.js', 'config/initializers/' + name + '.js');
};

And let’s execute our generator:

$ yeoman generate initializer core_extensions

Problems

• yeoman = require('../../../'); doesn't seem to work
• $ yeoman generate initializer core_extensions generate command doesn't exist. should be init?
• name is not defined

I'm guessing the offending line is:

Generator.prototype.copyInitializerFile = function() {
  this.copy('initializer.js', 'config/initializers/' + name + '.js');
};

Brad Neuberg from Inking gave me some quick feedback on yeoman.io landing page:

• Put the features list at the top, before the video. This should go right under the "Yeoman is a robust and opinionated set of tools..." so that someone can quickly see why they should care about Yeoman.
• Replace the video with something one minute long that is more marketing oriented, glossier, and which goes over the features rather than teaching someone how to use the package. I'd drop the longer educational video to the bottom of the page once someone is already bought into the framework.

Yeoman.io currently doesn't have any screencasts to help introduce folks to the project.

Let's change that 📹

I'd like to propose we start making changes to improve this by:

1. Adding http://www.youtube.com/watch?v=iUQ1fvdO9GY to the homepage (for now)
2. Recording a short introductory video to the project (1-3 mins). I'm happy to do this.
3. Identifying strong video coverage by members of the community and recommending some of them. Rob Levin has recorded a bunch of interesting stuff. Paul's video from Google I/O last year is still relevant.

What do we think?

If people are in agreement I'd like to discuss a few follow-up questions.

On 1: where should the video be embedded?
On 2: what would you like covered and what is the ideal video length you'd like?
On 3: should this be integrated into a 'videos' page of some sort?

Please use the new Bower logo, courtesy of desandro and isaac - http://i.imgur.com/QmGHPgc.png :). Thanks

Couple of examples:

Good header:

Bad Header:

We should clean all these up.

New site url is bower.io. The change will avoid the majority of the redirect circuit that is currently taking place.

We should of course use Yeoman to build our site. Me wants some dog food.

We'll wait until Yeoman 1.0 is released.

Specifically, npm install && bower install is needed.

If so, I'd totally switched to this stuff when it releases.

Now that get.yeoman.io has been replaced with a note to upgrade to Yeoman 1.0, we should at least take down the old installation guide. Is there any reason to keep the other parts of the 0.9 docs online?

http://yeoman.io/community-generators.html
https://yeoman-plugin-list.herokuapp.com/ is returning an error

Error in console:

XMLHttpRequest cannot load https://yeoman-plugin-list.herokuapp.com/. Origin http://yeoman.io is not allowed by Access-Control-Allow-Origin.

(the error response doesn't set the right headers...)

Hey guys, just wondering if anyone knew what might be going on here. I'm trying to do a clean install of Yeoman and keep getting these errors. I must admit I'm new to using frameworks like this, but I was able to install it without issue on my work computer...

I also followed the unintsall/reinstall instructions here to no avail: https://github.com/yeoman/yeoman/wiki/Additional-FAQ

npm install -g yeoman

npm http GET https://registry.npmjs.org/yeoman
npm http 200 https://registry.npmjs.org/yeoman
npm http GET https://registry.npmjs.org/yeoman/-/yeoman-0.9.5.tgz
npm http 200 https://registry.npmjs.org/yeoman/-/yeoman-0.9.5.tgz
npm ERR! error rolling back Error: EPERM, chmod '/usr/local/share/npm/bin/yeoman'
npm ERR! error rolling back [email protected] { [Error: EPERM, chmod '/usr/local/share/npm/bin/yeoman']
npm ERR! error rolling back errno: 50,
npm ERR! error rolling back code: 'EPERM',
npm ERR! error rolling back path: '/usr/local/share/npm/bin/yeoman' }
npm ERR! Error: EPERM, chmod '/usr/local/share/npm/bin/yeoman'
npm ERR! { [Error: EPERM, chmod '/usr/local/share/npm/bin/yeoman']
npm ERR! errno: 50,
npm ERR! code: 'EPERM',
npm ERR! path: '/usr/local/share/npm/bin/yeoman' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! System Darwin 12.2.0
npm ERR! command "/usr/local/Cellar/node/0.8.14/bin/node" "/usr/local/bin/npm" "install" "-g" "yeoman"
npm ERR! cwd /Users/justin
npm ERR! node -v v0.8.14
npm ERR! npm -v 1.1.65
npm ERR! path /usr/local/share/npm/bin/yeoman
npm ERR! code EPERM
npm ERR! errno 50
npm ERR! stack Error: EPERM, chmod '/usr/local/share/npm/bin/yeoman'
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /Users/justin/npm-debug.log
npm ERR! not ok code 0

Now, I realized "sudo npm install -g yeoman" does seem to install everything correctly without errors, but after it finished installing, i tried the command "yeoman"

yeoman
-bash: yeoman: command not found

A friend suggested this to fix it - "export PATH=/usr/local/share/npm/bin:$PATH", so now I can access "yeoman" commands, but it returns this message now instead:

yeoman
Starting update check...
EACCES, permission denied '/Users/justin/.config/npm-updater/yeoman.json'

At a bit of a loss here, like I said I was able to install it fine on another computer, but not this one. I'm probably just missing something?

EDIT: I manually changed the owner user of yeoman.json and I found out that in order to use yeoman commands I have to enter "export PATH=/usr/local/share/npm/bin:$PATH" in the terminal first, otherwise I get the -bash: yeoman: command not found error. Can anyone provide insight as to why? Thanks!

The site could use a little flexbox/responsive love. Screens taken on Chrome Beta 30/Android 4.3/N4

On this blog post, the link with anchor text Stephen's Building Apps With The Yeoman Workflow (under 'Why Yeoman' section) currently points to http://yeoman.io/blog/net.tutsplus.com/tutorials/javascript-ajax/building-apps-with-the-yeoman-workflow/ (404), but the correct link is http://net.tutsplus.com/tutorials/javascript-ajax/building-apps-with-the-yeoman-workflow/

Hi,

On the website, I get an error saying :
"Included file 'yeoman.wiki/docs/Getting-started-with-1.0.md' not found in _includes directory"

We get that error when going on all the pages of the "Getting Started" page for the 1.0 beta version.

Git add maybe ?

Best,
Thomas F.

Possibly related to commit 2669b10. The new data source is not correctly setting the Access-Control-Allow-Origin header in the request, so Chrome refuses to render the data.

Hello.

Reading the guide I saw little error in 'generators' section. You can see it on attached screenshot

The correct link is http://yeoman.io/generators.html

Coming back to a project I created a while ago and running yeoman server:
Starting update check...
Update available: 0.9.6 (current: 0.9.5)
Updating yeoman

The update process finishes successfully but running yeoman server again, generates:
Running "compass:dist" (compass) task
directory temp/styles/
error app/styles/main.scss (Line 450: Expected a color. Got: transparent)
create temp/styles/main.css
Task "compass:dist" failed. Use --force to continue.

Aborted due to warnings.

Should there be a temporary disclaimer indicating you'll need node 0.8+ for the install to succeed?

I ran the install with node @ v0.6.18 and NPM threw an error, but the success message still displayed. I figured it out fairly quickly, but it might cause confusion for some users?

Issue also referenced on the main project

This could be removed once there's a more reliable way to check node version.

I'm using the version of node from nodejs.org, not homebrew, and I had an outdated version, which meant the install script failed when it reached the stage where it installed the yeoman package from npm.

I'm assuming that if you have the homebrew version of node and it's out of date the upgrade happens automatically, and that it's not possible to upgrade the nodejs.org version from a script.

It's not a major issue and it's very easy to fix but I imagine some other people will run in to this so it might be worth showing an error if node is both out of date and the script can't update it.

Currently the npm install fails but the shell script keeps going and reports a successful install.

With yeoman/yo#25 landed, we no longer need to manually install bower and grunt-cli. This needs to be reflected in a few places:

(Feel free to edit the issue directly and add items here)

• yeoman.io: Homepage + Getting Started
• "yo generator: Getting Started" draft
• Generator READMEs?
• Publish homepage changes

Also, should we add a note for users of older npm versions?

i was really a bit shocked, when i realised that the project it self doesn't use it own piece of software. could somebody explain me why there is no use of grunt, bower or even yeoman?

Somehow, the fork banner is blocking scrolling unless you're very precise with how/where you scroll. We need to get this addressed otherwise our audience might be less patient than we are about getting through the homepage.

cc @ericduran

Yeoman uses https://github.com/SBoudrias/Inquirer.js/ for the prompt but doesn't have a very comprehensive documentation of all the available options.

I think the best solution is to link to the inquirer docs somewhere as currently you have to look at the source to find out which library is being used.

Hello yeoman team,
Knockout is very popular with lot of developers and it would be awesome to have knocout support in yeoman. Is that on the horizon?
Regards
Amit Varshney

Can probably submodule stuff in.. Would be really handy especially for all our FAQ data.

@zenorocha can you help with this?