-
Notifications
You must be signed in to change notification settings - Fork 0
Additional FAQ
Note: The documentation below is for an older version of Yeoman and has been deprecated.
Below you can find common questions and answers to recent issues. We'll be adding these to our main FAQ page on yeoman.io shortly.
To get a prerelease version of Yeoman, you can install from git master. This is also recommended for developing Yeoman.
sudo npm uninstall yeoman -g # if you experience problems, read below...
git clone https://github.com/yeoman/yeoman.git
cd yeoman/cli
sudo npm install -g
sudo npm link # links your global yeoman binary to this folder locationas of yeoman 0.9.6 the contents of cli have been moved to the root yeoman directory. Step 3 above would be:
cd yeomanThis was an issue in Yeoman 0.9 and is fixed in master. Follow the instructions above to manually update your local installation to master.
It's likely your PATH does not account for global NPM modules just yet. Better documentation forthcoming but until then, read this comment and this thread.
This usually happens when you install Node through Homebrew, since it puts Node modules in a directory that's not in your PATH.
From Homebrew:
==> Caveats
Homebrew installed npm.
We recommend prepending the following path to your PATH environment
variable to have npm-installed binaries picked up:
/usr/local/share/npm/bin
Quick fix for advanced users is to put the following in your .bashrc/.zshrc file:
export PATH=/usr/local/share/npm/bin:$PATH
For beginners brew uninstall node and download and install Node from their website.
See the answer to the first question.
EMFILE mean you've reached the OS limit of concurrently open files. There aren't much we can do about it, however you can increase the limit yourself.
Add ulimit -n [number of files] to your .bashrc/.zshrc file to increase the soft limit.
If you reach the OS hard limit, you can follow this StackOverflow answer to increase it.
With 0.9.1, coffescript file are now handled through grunt-contrib-coffee, and thus the old configuration, contained in your project Gruntfile.js is deprecated.
To fix the issue replace your old coffee config, but something like:
coffee: {
compile: {
files: {
'app/scripts/build/*.js': 'app/scripts/**/*.coffee'
},
options: {
basePath: 'app/scripts',
flatten: true
}
}
},
(see the grunt-contrib-coffee for additional documentation).
Additionally the watch config related to coffee files needs to be updated from:
watch: {
coffee: {
files: <config:coffee.dist.src>,
tasks: 'coffee reload'
},
to
watch: {
coffee: {
files: 'app/scripts/**/*.coffee',
tasks: 'coffee reload'
},
That is as intended. Since the update check run daily, we don't want to disrupt your flow, so your previous action continues after the update check and/or update, which uses the old version loaded in memory. The next time you use Yeoman you'll be using the updated version.
Please refer to the wiki page How to control yeoman server and build tasks from Gruntfile.js.
View the details within #152 ticket for recommended solutions for documentation generation
It keeps the IP clean and helps to prevent frivolous lawsuits around who owns what software. Basically the thing all of us want to avoid anyhow. In summary, the CLA asserts that when you donate fixes or documentation, you both own the code that you're submitting and that Google can in turn license that code to other people. (In this case, making it available under the BSD license)
So yeah it's an extra hurdle, but it's something we can't avoid here. This is a Google open source project and thems are the rules.
Just FWIW, here are some other projects that require a similar agreement, jQuery, Firefox, Sizzle, Dojo, Plone, Fedora, Cordova/Phonegap, Apache, Flex.
More: