Inquirer

- Replace `chalk` with ~`picolors`~ (in 9.3.2 went to `yoctocolors` to stay with Sindre's packages and reduce amount of provenance.)
- Drop many dependencies in favour of native functions when possible.

No impact expected, but it's a large changes in dependencies. Let us know if you run into any issues upgrading!

inquirer/prompts5.0.7
- Replace `chalk` with ~`picolors`~ (in 5.1.0 went to `yoctocolors` to stay with Sindre's packages and reduce amount of provenance.)
- TS 5.5 (no impact expected on package users)

inquirer/password2.1.10
* Fix whitespace inconsistencies 1411

inquirer/core8.2.3
* Performance improvements to `usePrefix()` when switched to loading mode. There's now a little delay of 300ms before displaying the loader to avoid flickering when fast validation occurs.

- `editor` prompt: Fixed compatibility issue between `default` and `waitUserInput` options. 1405

inquirer/core8.2.0
- `makeTheme` now performs deep merges of the theme objects.

inquirer/core8.1.0
- [Typescript] `useState` doesn't require a default value anymore; in which case it'll default to `undefined`
- [Typescript] `useRef` doesn't require a default value anymore; in which case it'll default to `undefined`

Examples:

ts
const [value, setValue] = useState<number>();
// value: number | undefined;

const [value, setValue] = useState<number>(1);
// value: number;


inquirer/prompts5.0.1
- Fix: breaking change wrongly removed the `Separator` export.

- On windows, we will now use unicode characters whenever possible

inquirer/select2.3.0
- Help tip behaviors are now customizable through theme options.

inquirer/prompts5.0.0
- [Breaking 1384] `inquirer/core` isn't exported from `inquirer/prompts` anymore. If you want to create custom prompts, import from the core package. This decision was made to disambiguate what breaks in each package - with prompts re-exporting core, any core breaking change (no matter how minor) caused a major version bump. Now only prompts interfaces breaking changes will be major on prompts. We're hoping this will simplify your usage of `inquirer/*` packages.

inquirer/prompts4.3.3
- On windows, we will now use unicode characters whenever possible

inquirer/figures1.0.0
- Fork of [figures](https://github.com/sindresorhus/figures) to get new features and CJS support. We plan on maintaining it ourselves for now.

inquirer/core8.0.0
- [Breaking] `usePagination()` doesn't return help tips anymore (and also doesn't take a `theme` argument anymore.) Help tips are now solely the responsibility of prompt implementation.

inquirer/checkbox2.3.0
- Help tip behaviors are now customizable through theme options.

inquirer/prompts4.3.2
- Performance improvements (less flickering mainly noticeable on select/checkbox)

inquirer/input2.1.1
- Bugfix: Cursor position when no value/default value is rendered.
- Chore: Dependency bumps

inquirer/prompts4.3.0
- Errors thrown from prompts are now custom errors.

inquirer/core7.1.0
- Feat: Thrown errors from Inquirer are now all custom (so they can be filtered.) Those errors are exported from the package.

inquirer/prompts4.2.1
- Bugfix: When relying on asynchronous validation, the loader icon was broken.
- Chore: Added tests covering the prior issue to prevent future regression of loaders.

inquirer/core7.0.2
- Bugfix: `usePrefix` returned broken loader frames (bug introduced with the themability capabilities)
- Chore: Added tests covering the prior issue to prevent future regression.

inquirer/select2.1.0
* `inquirer/select` now support search when typing letters (aiming to imitate how the HTML `<select>` search works)

inquirer/checkbox2.1.0
- Allow customizing `renderSelectedChoices` with theme.

inquirer/prompts4.0.0
- All prompts are now themable. See each prompts documentation about the options available.
- BREAKING: The `message` option of each prompt must now be a `string`. It could previously be an asynchronous function. See [recipes for a migration option](https://github.com/SBoudrias/Inquirer.js#wait-for-config).
- Node 18 required

inquirer/core7.0.0
- Now exposes utilities to allow theming prompts (`type Theme`, `makeTheme`)
- `message` option isn't transformed by the core anymore - options are now passed through as-is to the prompt.
- Node 18 required

inquirer/core6.0.0
- Breaking: `usePagination` now requires `pageSize` to be passed in. The size of the pages should inform the help shown on the screen, and keeping this information in 2 areas leave a change the default value will mistmatch.

inquirer/checkbox1.5.0
New features!

- New `required` prompt config. Makes sure at least one choice is selected.
- New `validate` prompt config. Provide a function that'll validate the user selection with any logic you want (like enforcing a min or max selection amount.) Please use this config with parsimony since complicated validation scheme can lead to sub-optimal UX!

inquirer/select1.3.0
- Now supports the `loop: false` option. (This feature was available on `inquirer`, but not ported to new prompts yet)

inquirer/core5.1.0
- Introduces a new `useMemo` hook.

inquirer/checkbox1.4.0
- Now supports the `loop: false` option. (This feature was available on `inquirer`, but not ported to new prompts yet)

inquirer/core5.0.1
- Bugfix: infinite loop occurring when changing state from `useEffect` body. See 1307

inquirer/prompts3.1.1
- Fix: There was an issue with ESM/CJS imports interoperability that should now be fixed. Ref 1297

inquirer/core5.0.0
- Breaking (low chance): The typing always defined a `validate` config; but it was rarely used. It's been removed and prompts relying on it are expected to handle it on their own (no default value.) The types were updated accordingly and will raise issue if you're using typescript.
- Deprecation warning (TS only): If your custom prompt extended `AsyncPromptConfig`, it's been deprecated in favour of `PromptConfig`

diff
- import type { AsyncPromptConfig } from 'inquirer/core';
+ import type { PromptConfig } from 'inquirer/core';

- type Config = AsyncPromptConfig & { custom: 'value' };
+ type Config = PromptConfig<{ custom: 'value' }>;


Note: Old interface works for now, but is marked as deprecated.

inquirer/prompts3.1.0
- Review how force exit events are handled to make sure we restore the cursor properly.
- Various dependencies bump (including TS 5.2.2)

inquirer/core4.1.0
- Review how force exit events are handled to make sure we restore the cursor properly.
- Various dependencies bump (including TS 5.2.2)

inquirer/core4.0.0
Major rewrite of the core to rely on [node's async hooks](https://nodejs.org/api/async_hooks.html) for better isolation of each prompts. Relying on this means each prompt context is fully isolated (previously it would rely on the module level context.)

We expect this update to be transparent to most. Though some custom event handlers within `useEffect` could stop working. If you find any issues there, first please let us know - there might be thing to improve internally to make it transparent. The manual fix will likely be to explicitly define events callback as an [AsyncResource](https://nodejs.org/api/async_context.html#integrating-asyncresource-with-eventemitter).

Let us know how this works for you!

inquirer/core3.1.2
- Fix bug where a `setState` call triggered from `useEffect` might re-render the screen with the previous state.

- Modified lodash imports to help with tree-shaking
- Replace unmaintained `through` dependency (only affect users of the old bottom bar)

inquirer/password1.1.6
Bugfix: Cursor position now reflected properly when using arrow keys.

inquirer/input1.2.6
Bugfix: Cursor position now reflected properly when using arrow keys.

inquirer/core3.1.0
- Bugfix (and insuing refactor) of how the cursor position is maintained and handled when changing outside of a render cycle. This caused bugs with all underlying prompts where the user input text. This fix should be transparent for all users; but it is a large change so warranted a minor bump.

inquirer/select1.2.5
- Choice list max width should always match the terminal width

inquirer/prompts3.0.0
- Breaking: Includes new major version of `inquirer/core`.
- Bug fix: on Select & Checkbox prompt where it could happen the choice list wasn't matching the terminal width.

inquirer/core3.0.0
- Breaking: `Paginator` is deprecated in favour of the `usePagination` hook. This hook will always properly reflect the width of the output stream.

inquirer/checkbox1.3.5
- Choice list max width should always match the terminal width

inquirer/prompts2.3.1
Fix bug where Common.js Typescript types definition were broken (should have no impact on ESM users)

inquirer/testing2.1.0
- New `getFullOutput()` utility that'll return a raw string of everything that was written to the output stream
- Ignore cursor hide/show ANSI code from raw output (keeping those made it harder to test raw output where those cleaning code would always be the only result due to how inquirer clean state.)

inquirer/core2.3.0
- Fix bug where multiple prompts were allowed to run at the same time (and thus leak state)
- Fix bug where a failed prompt state could leak to subsequent runs of other prompts

inquirer/prompts2.2.0
- Performance improvements
- Includes updates in `inquirer/core2.2.0`

inquirer/core2.2.0
- When setting a state (`useState`), it'll only re-renders if the value changed.
- When setting multiple states at once, we'll only trigger one re-renders if it happens inside a hook callback (previously each state change triggered one re-render.)

If you're setting multiple state in a callback from an async function (like `setTimeout` or a network call), those will not be merged in a single re-renders. For those case, you're better using a state object holding all values to reduce the amount of re-renders. Open to discuss this in 1251

inquirer/editor1.2.0
Now exposes the `waitForUserInput` option. Setting it to false will automatically launch the editor.

Be careful using this option as this mean the user will not have read the question/instruction before reaching the editor.

inquirer/core2.1.0
`useEffect` now pass the active Readline instance to the effect callback. e.g `useEffect((readline) => ...`

inquirer/testing2.0.0
Rewrote how raw input is handled. This shouldn't cause issue for most, but if you had specific or uncommon use of the testing framework, this could be a breaking change.

inquirer/core2.0.0
Major refactor of the core to allow multiple features:

1. Prompt function now return cancelable promise (e.g `input(...).cancel()`)
2. Reduced amount of writes to the readline (should now be ~1 per render cycle)
3. Make sure to restore the cursor on force exit.

inquirer/confirm2.0.0
Now includes a stricter answer parser. Prior to this change, the prompt would default to `Yes` on almost any input.

Fix issue with the default value disappearing from prompt.

Inquirer is now a native Node ECMAScript module. This will require your Node runtime to support es modules, and your app to be an es module. Node documentation over here: https://nodejs.org/api/esm.html#modules-ecmascript-modules

If you cannot migrate, please remember you can keep using the v8.x release line until you're ready.