- 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.