Skip to content

[Snyk] Security upgrade inquirer from 8.2.4 to 9.3.0#1274

Open
mshanemc wants to merge 1 commit into
mainfrom
snyk-fix-e8dae70f32d946b906f432458f25e5c9
Open

[Snyk] Security upgrade inquirer from 8.2.4 to 9.3.0#1274
mshanemc wants to merge 1 commit into
mainfrom
snyk-fix-e8dae70f32d946b906f432458f25e5c9

Conversation

@mshanemc
Copy link
Copy Markdown
Contributor

@mshanemc mshanemc commented Apr 1, 2026

snyk-top-banner

Snyk has created this PR to fix 3 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • examples/package.json
  • examples/yarn.lock

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Arbitrary Code Injection
SNYK-JS-LODASH-15869625
  716  
medium severity Prototype Pollution
SNYK-JS-LODASH-15869619
  631  
medium severity Prototype Pollution
SNYK-JS-LODASH-15053838
  559  

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Prototype Pollution
🦉 Arbitrary Code Injection

@mshanemc
Copy link
Copy Markdown
Contributor Author

mshanemc commented Apr 1, 2026

Merge Risk: High

The upgrade from inquirer v8 to v9 is a major version change with a significant breaking change related to its module format.

Key Breaking Change: Switch to pure ESM

Inquirer v9+ is distributed as a native ECMAScript module (ESM). This means you can no longer import it using the CommonJS require() function. [6, 7]

  • Old code (v8): const inquirer = require('inquirer');
  • New code (v9): import inquirer from 'inquirer';

This change will break any project that has not been configured to support ESM modules. To resolve this, you may need to update your project's package.json to include "type": "module" or change file extensions to .mjs.

Recommendation: This upgrade requires code changes for importing the module and potentially a project-wide shift to the ESM module system. Before merging, you must update your code to use import instead of require and ensure your environment supports ESM. Alternatively, you can remain on version 8 until you are ready to migrate your project to ESM. [6]

Source: GitHub Discussion, Stack Overflow

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

@mshanemc mshanemc requested a review from a team as a code owner April 1, 2026 11:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants