fix(deps): update dependency yeoman-generator to v4 #36
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^2.0.0
->^4.0.0
Release Notes
yeoman/generator
v4.1.0
Compare Source
--bail
flag who'll exit the generator as soon as a conflict occurs.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
Compare Source
v4.0.1
Compare Source
v4.0.0
Compare Source
Breaking
v3.2.0
Compare Source
Added a new optional syntax to use
composeWith
:v3.1.1
Compare Source
Fix some issues with
--force-install
not being detected properly from the command line arguments.v3.1.0
Compare Source
Add
--force-install
flag which will cause the generator to throw if the installation phase fail.v3.0.0
Compare Source
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.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.runInstall
toscheduleInstallTask
New
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)Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "
rebase!
".🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot. View repository job log here.