[Snyk] Fix for 1 vulnerabilities

[Exnadella]

User description

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• packages/bundler/package.json
• packages/bundler/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Regular Expression Denial of Service (ReDoS) SNYK-JS-ACORN-559469	589

---

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:

🦉 Regular Expression Denial of Service (ReDoS)

---

PR Type

Bug fix, Enhancement

---

Description

• Updated espree and rollup dependencies in package.json to address a Regular Expression Denial of Service (ReDoS) vulnerability.
• Synchronized package-lock.json with the updated dependencies to ensure consistency.

---

Changes walkthrough 📝

	Relevant files
Dependencies	package.json Update dependencies to fix vulnerabilities                              packages/bundler/package.json Updated espree version from ^3.5.2 to ^6.2.1. Updated rollup version from ^1.3.0 to ^2.0.0. +2/-2      package-lock.json Synchronize package-lock with updated dependencies              packages/bundler/package-lock.json Updated lock file to reflect changes in package.json. +1972/-1949
Additional files (token-limit)	package-lock.json ...                                                                                                            packages/bundler/package-lock.json ... +1972/-1949

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[qodo-merge-pro]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No key issues to review

[qodo-merge-pro]

PR Code Suggestions ✨

Category	Suggestion	Score
Dependency update	Update the espree dependency to a more recent version Update the espree dependency to a more recent version (6.2.1) to benefit from bug fixes and potential performance improvements. packages/bundler/package.json [30] -"espree": "^3.5.2", +"espree": "^6.2.1", Apply this suggestion Suggestion importance[1-10]: 9 Why: The suggestion correctly identifies the update of the espree dependency from version 3.5.2 to 6.2.1, which is reflected in the PR code diff. This update is important for taking advantage of bug fixes and performance improvements.	9
	Update the rollup dependency to a major new version Update the rollup dependency to version 2.0.0 or later to take advantage of new features and improvements in the bundling process. packages/bundler/package.json [35] -"rollup": "^1.3.0", +"rollup": "^2.0.0", Apply this suggestion Suggestion importance[1-10]: 9 Why: The suggestion accurately reflects the update of the rollup dependency from version 1.3.0 to 2.0.0, as shown in the PR code diff. This update is significant for leveraging new features and improvements in the bundling process.	9

[qodo-merge-pro]

CI Failure Feedback 🧐

(Checks updated until commit 09b8110)

Action: test (ubuntu-latest)

Failed stage: Run npm run bootstrap [❌]

Failed test name: ""

Failure summary: The action failed due to an error during the npm ci command execution in the wct-mocha package: The command npm ci exited with code 1, indicating a failure. There are multiple deprecation warnings for packages used in the project, which may contribute to the failure.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 555: npm WARN deprecated [email protected]: Glob versions prior to v9 are no longer supported 556: npm WARN deprecated [email protected]: This package is no longer supported. 557: npm WARN deprecated [email protected]: This module is no longer supported. 558: npm WARN deprecated [email protected]: This package is no longer supported. 559: npm WARN deprecated [email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. 560: npm WARN deprecated [email protected]: This package is no longer supported. 561: npm WARN deprecated [email protected]: This package is no longer supported. 562: npm WARN deprecated @lerna/[email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. 563: npm WARN deprecated @lerna/[email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. ... 738: npm ERR! [-ws|--workspaces] [--include-workspace-root] [--install-links] 739: npm ERR! 740: npm ERR! aliases: clean-install, ic, install-clean, isntall-clean 741: npm ERR! 742: npm ERR! Run "npm help ci" for more info 743: npm ERR! A complete log of this run can be found in: 744: npm ERR! /home/runner/.npm/_logs/2024-09-05T15_51_57_989Z-debug-0.log 745: lerna ERR! npm ci exited 1 in 'wct-mocha' 746: ##[error]Process completed with exit code 1.

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.