graphql-code-generator fix(deps): update dependency inquirer to v12

fix(deps): update dependency inquirer to v12

Open renovate[bot] opened this issue 9 months ago • 2 comments

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
inquirer (source)	`^8.0.0` -> `^12.0.0`

Release Notes

SBoudrias/Inquirer.js (inquirer)

`v12.3.0`

Compare Source

Checkbox prompt: re-added support for an array of default to be provided listing pre-checked checkboxes. This is a legacy interface brought back given this feature removal was an involuntary breaking change during the v12 release. The preferred interface is to provide the checked property to choices { value: 'bar', checked: true }.

`v12.0.0`

Compare Source

@types/node is now only a peerDependencies. This reduces the install size of inquirer dramatically for folks not using Typescript. It's unlikely to break your builds if you used TS already, if it does run npm install --dev @types/node/yarn add --dev @types/node.

`v11.1.0`

Compare Source

Now exports base utility Typescript types: import type { Question, DistinctQuestion, Answers } from 'inquirer';

You should use as follow to keep the inference working properly:

const questions = [
    { ... }
] as const satisfies Question[];
// If you're not using inquirer plugins, `Question` could alternatively be replaced by `DistinctQuestion` for stricter checks.

`v11.0.2`

Compare Source

Fix #1555: when behaviour changed unexpectedly when returning a falsy value.

No technical breaking changes; but we changed the style of the question prefix once the answer is provided. Once a question is answer, the prefix becomes a tick mark (previously it was the same ? as when the prompt is idle.)

This is theme-able, and so can be overwritten to with theme.prefix.

`v10.2.2`

Compare Source

Fix the filter option not working.
The signal: AbortSignal didn't work with class based prompts (OSS plugins.) Now it should work consistently with legacy style prompts.

`v10.2.1`

Compare Source

Fix expand prompt being broken if a Separator was in the choices array.

`v10.2.0`

Compare Source

Includes various fixes & new features to the different built-in prompts
Fix: Major rework of the Typescript types. Hoping to reduce the amount of finicky type errors (or wrong types) you might've ran into.

Fix broken backward compatibility issues with v9. Choice objects without value should default to use name as the value. Note: Please don't rely on this weird behaviour, but we fixed it since it was an unintended breaking change.

`v10.1.1`

Compare Source

`v10.1.0`

Compare Source

Adds the new { type: 'search' } prompt.

`v10.0.4`

Compare Source

`v10.0.3`

Compare Source

`v10.0.2`

Compare Source

`v10.0.1`

Compare Source

`v10.0.0`

Compare Source

Re-implemented with Typescript.
Adding CJS support (now inquirer is publishes a dual-build CJS/ESM.)
All core prompts are now coming from @inquirer/prompt.
Custom prompts now should be implemented with @inquirer/core. Custom prompts built on [email protected] will keep working, but should plan a migration.
inquirer.ui.BottomBar is deleted.

My expectation is that this release should be a drop-in replacement for people using inquirer.prompt() and built-ins 🤞🏻. Please open an issue on Github if you run into issues migrating; it's a large rewrite and there might be a few sharp edges to cut! Hope you'll like this new release.