v0.19.2

Fix bug with this.extract() where the method would create an empty tarball.

v0.19.1

• Fix issue with RunContext#withOptions() where name wouldn't be normalized to both camel and kebab case. We now convert names to both style to provide a more reliable behavior.

v0.19.0

Towards yeoman-generator 1.0.0

This is our first deprecation release. This release is marking a bunch of now deprecated methods and their replacement.

All deprecated methods should still work as expected, but they'll print a deprecation warning in the console. Rely on these messages to find and replace deprecated methods you might be using in your generators.

If you're building a brand new generator, then you needn't worry.

To follow our deprecation policy, please join the discussion. (You can click the subscribe button on the right toolbar to follow further discussions)

v0.18.10

Fixes

1. #installDependencies() now run npm install first, then bower install.
2. Added support for EcmaScript 2015 (previously named ES6) class syntax:

module.exports = class MyGenerator extends generators.Base {}

v0.18.9

• Allow file writes to occurs after the writing phase. (Fix #758)

v0.18.8

• Fix bug where calling generator#spawn_command() without options wouldn't inherit the stdio by default.

v0.18.7

• Use the memory file-system inside the Gruntfile API
• Fix bug where custom generator description could be lost
• Improve debug logging (refer to readme for up to date documentation)
• Diffing module now support binary files (during conflicts)

Plus a general cleanup of core API and stricter usage of parameters.

v0.18.6

Fixes an issue occuring after an update in mem-fs-editor

v0.18.5

Bug fixes

• Fix bug where selecting skip option during a conflict resolution was ignored (every files were written to disk)

Feature Updates

• RunContext now take a settings.tmpdir boolean value. When set to false, it won't automatically run a generator inside a temporary directory. This feature is only provided to ease the upgrade of some generators; you really shouldn't ever need to use this option. If your test only pass on not cleaned up directory, this mean you have a coupling issue in your test and you're making them flakey. Please refer to http://yeoman.io/contributing/testing-guidelines.html for guidelines on how to keep your tests isolated.

v0.18.4

feature update

• RunContext#inTempDir() now accepts a callback