Releases: yeoman/generator
Releases · yeoman/generator
v4.3.0
v4.2.0
- New feature: Support diffing to ignore whitespace change
yo node --no-whitespace
- New feature:
Generator#composeWith()
can now be called with an array of generators. - Bugfix: Fixes bug when a generator default export is under
exports.default
(like when compiling es6 modules with Babel) -
- some other minor fixes and improvements
v4.1.0
- New
--bail
flag who'll exit the generator as soon as a conflict occurs. - New
generator#queueMethod()
allows generator to programmatically schedule tasks on the queue. This can be useful for parents generator who're inherited by children generators to schedule some default tasks automatically. (not a very common use, but might be useful in some edge cases)
v4.0.2
v4.0.0
Breaking
- Officially supports Node >= 8 (dropped support for Node 6)
- Install methods will be run 1 time per set of arguments. Previously we'd only run them once no matter the arguments, this prevented use case like different npm settings for more complicated setup with different targets (server/browser) #1108
v3.2.0
v3.1.1
v3.1.0
v3.0.0
Maintenance release with a few breaking change that shouldn't impact most users.
Breaking
mem-fs-editor
updated to latest release. A sub-dependency moved fromnode-glob
tofast-glob
, so some of thethis.fs
methods glob options will change.- Install methods:
npmInstall
,bowerInstall
,yarnInstall
andinstallDependencies
do not return promises anymore. This behavior was confusing and a major source of bugs. To handle actions after the install might've run (if user didn't specify--skip-install
), use theend
run loop phase. - Renamed
runInstall
toscheduleInstallTask
New
- For users of the Yeoman API:
generator.run()
now returns a promise as well as taking a callback (the callback will keep working for the foreseeable future as we need to maintains backward compatibility with older generators)