Skip to content

npm(deps): bump inquirer from 9.3.8 to 13.3.2#333

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/main/inquirer-13.3.2
Open

npm(deps): bump inquirer from 9.3.8 to 13.3.2#333
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/main/inquirer-13.3.2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Apr 1, 2026

Copy link
Copy Markdown
Contributor

Bumps inquirer from 9.3.8 to 13.3.2.

Release notes

Sourced from inquirer's releases.

inquirer@13.3.2

  • Fix broken 1.3.1 release process.

inquirer@13.2.5

What's Changed

New Contributors

Full Changelog: https://github.com/SBoudrias/Inquirer.js/compare/inquirer@13.2.2...inquirer@13.2.5

inquirer@13.2.4

What's Changed

... (truncated)

Commits
  • b218fcc chore: Publish new release
  • b6aabed fix: set prepublish script
  • 1ce0319 chore: Publish new release
  • 62a1b2d Merge pull request #2031 from SBoudrias/sboudrias/debug-xterm-80g
  • 09fcc6c chore(@​inquirer/testing): fix formatting
  • 56bdf30 fix(@​inquirer/testing): resolve xterm CJS named export error under native Nod...
  • 58d3bf0 chore(deps): Bump brace-expansion from 1.1.11 to 1.1.12 (#2029)
  • f9a3adb Merge pull request #2026 from SBoudrias/emdash/semver-315
  • 264f5da chore(setup-packages): simplify coerce using tryParseRange
  • feab678 chore(setup-packages): replace semver with std-semver
  • Additional commits viewable in compare view

Dependabot compatibility score

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor 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)

Bumps [inquirer](https://github.com/SBoudrias/Inquirer.js) from 9.3.8 to 13.3.2.
- [Release notes](https://github.com/SBoudrias/Inquirer.js/releases)
- [Commits](https://github.com/SBoudrias/Inquirer.js/compare/inquirer@9.3.8...inquirer@13.3.2)

---
updated-dependencies:
- dependency-name: inquirer
  dependency-version: 13.3.2
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Apr 1, 2026
@dependabot dependabot Bot requested a review from ttsukagoshi as a code owner April 1, 2026 06:05
@dependabot dependabot Bot added the javascript Pull requests that update Javascript code label Apr 1, 2026
@github-actions

github-actions Bot commented Apr 1, 2026

Copy link
Copy Markdown

Coverage report

Caution

Coverage does not meet threshold
Statements coverage not met for global: expected >=100%, but got 41.51925078043705%

St.
Category Percentage Covered / Total
🔴 Statements
41.52% (-58.48% 🔻)
399/961
🟢 Branches
93.88% (-6.12% 🔻)
46/49
🟡 Functions
65% (-35% 🔻)
13/20
🔴 Lines
41.52% (-58.48% 🔻)
399/961
Show files with reduced coverage 🔻
St.
File Statements Branches Functions Lines
🔴
... / convert.ts
0% (-100% 🔻)
0% (-100% 🔻)
0% (-100% 🔻)
0% (-100% 🔻)
🔴
... / init.ts
0% (-100% 🔻)
0% (-100% 🔻)
0% (-100% 🔻)
0% (-100% 🔻)
🟢 src/messages.ts
92.42% (-7.58% 🔻)
100%
20% (-80% 🔻)
92.42% (-7.58% 🔻)
🔴 src/utils.ts
0% (-100% 🔻)
0% (-100% 🔻)
0% (-100% 🔻)
0% (-100% 🔻)

Test suite run failed

Failed tests: 0/27. Failed suites: 3/9.
  ● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation, specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /home/runner/work/csv2gsheets/csv2gsheets/node_modules/@inquirer/prompts/dist/index.js:1
    export { default as checkbox, Separator } from '@inquirer/checkbox';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

       7 | import { C2gError } from '../src/c2g-error';
       8 | import * as constants from '../src/constants';
    >  9 | import inquirer from 'inquirer';
         | ^
      10 | import { MESSAGES } from '../src/messages';
      11 | import * as utils from '../src/utils';
      12 |

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1318:40)
      at Object.<anonymous> (node_modules/inquirer/dist/index.js:5:1)
      at Object.<anonymous> (test/utils.test.ts:9:1)


  ● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation, specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /home/runner/work/csv2gsheets/csv2gsheets/node_modules/@inquirer/prompts/dist/index.js:1
    export { default as checkbox, Separator } from '@inquirer/checkbox';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

      2 |
      3 | import fs from 'fs';
    > 4 | import inquirer from 'inquirer';
        | ^
      5 |
      6 | import * as auth from '../src/auth';
      7 | import login from '../src/commands/login';

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1318:40)
      at Object.<anonymous> (node_modules/inquirer/dist/index.js:5:1)
      at Object.<anonymous> (test/init.test.ts:4:1)


  ● Test suite failed to run

    src/utils.ts:5:20 - error TS2614: Module '"inquirer"' has no exported member 'QuestionCollection'. Did you mean to use 'import QuestionCollection from "inquirer"' instead?

    5 import inquirer, { QuestionCollection } from 'inquirer';
                         ~~~~~~~~~~~~~~~~~~

Report generated by 🧪jest coverage report action from f36b70f

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant