Bump yeoman-generator from 2.0.3 to 3.2.0

[dependabot-preview]

Bumps yeoman-generator from 2.0.3 to 3.2.0.

Release notes

Sourced from yeoman-generator's releases.

v3.2.0

Added a new optional syntax to use composeWith:

this.composeWith({
    Generator: require('generator-x'),
    path: require.resolve('generator-x')
})

v3.1.1

Fix some issues with --force-install not being detected properly from the command line arguments.

v3.1.0

Add --force-install flag which will cause the generator to throw if the installation phase fail.

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 from node-glob to fast-glob, so some of the this.fs methods glob options will change.
• Install methods: npmInstall, bowerInstall, yarnInstall and installDependencies 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 the end run loop phase.
• Renamed runInstall to scheduleInstallTask

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)

v2.0.5

Output more useful information to end user when a command fails or is skipped.

v2.0.4

• efc52c99 Change options and args order (#1063)

Commits

• 3bbeef0 3.2.0
• 8111562 Bump dependencies
• 1fd0d5f Bump dev dependencies
• ac944f7 Overload composeWith method to allow a generator class along its path (#1099)
• 1cd1031 Check if run callback is specific before setting it as the promise handler
• 392fd5d 3.1.1
• 93ad4e0 force-install is not used properly #1082 (#1083)
• db0e153 3.1.0
• 74ada52 scheduleInstallTask should fail incase installer fails and --force-install op...
• 68d7da1 Fix test on Windows (#1078)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge
• @dependabot reopen will reopen this PR if it is closed
• @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

[dependabot-preview]

Superseded by #85.