0.14.0 changelog (WIP)

[SBoudrias]

Generator system

New Features

• Copying large folder could cause a recursion error. Two new methods (generators.bulkCopy and generators.bulkDirectory) have been added to allow large folder being copied without template and conflict processing on each contained file. (example use case: transferring every file in the Wordpress repo) (Yeoman Generetor Crashes Because of endless recursion #350)
• Added a new file handling system. Generator now get access to this.src and this.dest who're scoped file utility relative to the sourceRoot and destinationRoot. The file utility is based on the Grunt.file interface but add scope and filters (write filters to beautify, transcode, etc and validate filters to check conflicts). (For examples and discussion see Add scoped helpers environments from file-utils #378 and Improvement to core file utility #313)

Bugs

• Fix bug with arguments inversed in the wiring methods (Broken wiring helpers #174)
• Fix bug causing the end event to be triggered multiple time (Bug 'end' emitted multiple times on overwriting files. #302 -> Fix Adding failing tests for end event firing multiple times when copying a file more than once. #402)
• Options/args passed to runHook are now cloned, so the hooked generator won't modify the state of these objects in the main one.
• generators fetching methods like extract, fetch, tarball now rely on the NPM download module.

Runner system (Environment)

• Fix and improve env.help output (Help weirdness #364 and Help improvements #398)
• Now detect correctly symlinked npm modules (e.g. using npm link)
• breaking env.register now only take a string (filepath or NPM module name) to make sure the metadata it assign to the generator are relevant (namespace, resolved). If you want to register a stubbed generator for easy testing, then use env.registerStub, but know the metadata might be missing or erroneous.
• breaking Removal of env.remote and env.engine. This shouldn't change anything as they were broked or not used.

Maintenance

• Added support for test coverage using Coveralls reports.
• Way better support for running test suite on Windows. It should run now.

See all: v0.13.4...v0.14.0-rc.2

[sindresorhus]

Nice work @SBoudrias. lgtm

Lets do another RC after we've merged the current 3 PRs.

[SBoudrias]

Yeah, there's also #387 who's a breaking change we should fix IMO.

[sindresorhus]

Agreed

[SBoudrias]

Ok, pushed back request method to fix #387.

I guess once we merge #377 we'd be ready!

[addyosmani]

SGTM. In the changelog, for anything we're removing which has the potential to break existing generators could we add a note calling that out? For the most part the changelog appears to be additions and fixes otherwise.

[SBoudrias]

I added marks to what is a breaking change, and updated the changelog with the latest change (which was only fixing a regression).

I think we should release 0.14 once #377 is merged.

[sindresorhus]

@SBoudrias agreed

[SBoudrias]

Merged #377 yesterday evening. Should be good for a release; cc @passy @sindresorhus @addyosmani

[addyosmani]

Let's spend a little time testing this further against master on some of our generators. Assuming everything works as expected, release away!

[addyosmani]

oh, and great work, Simon! :)

[addyosmani]

We're currently at RC2 for the generator system. I'd love to cut and tag a release for 0.14.0 final at the weekend as I haven't seen any major blockers to date.

Do we currently feel we're stable enough to do this?

[SBoudrias]

What should be fixed:

• Checkout Namespace resolving issue #406 (potential bug with namespace creation - seems limited to tests)
• Files helpers to handle binary file conflicts (Fix in file-utils 0.1.4)
• Conflicters to output links relative to CWD or destinationRoot (?? it is more esthetic, but... it is less accurate) (PR Ensure relatives path when resolving conflicts #409)

[SBoudrias]

Reported bug been fixed.

There've been a cosmetic issue about paths in the conflicters not being relative anymore - I'm not sure this is an issue as relative path are error prone (CWD can change and be inexact). Anyway, this issue is addressed in PR #409, we'll have to see what we do about it.

[SBoudrias]

Yo 1.0.5 got released using the unstable 0.14 and the rc2 holded a bug fixed this week. yeoman/yo#104

I think we should either release 0.14 or 0.14.0-rc3 as soon as possible.

[passy]

Is there anything holding us back from releasing generator master as 0.14?

[SBoudrias]

I think we should be good after merging the relative path PR for conflicts.

[SBoudrias]

Ok, so, my guess is we're ready for pushing 0.14.0 out of the gate

RC-1 and 2 have been tested on the outside and we had some bug reports, all are fixed.

[SBoudrias]

Changelog moved here: https://github.com/yeoman/generator/releases/tag/v0.14.0