[Snyk] Security upgrade @testing-library/jest-dom from 5.17.0 to 6.0.0

[as1605]

User description

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

Snyk changed the following file(s):

• example/package.json
• example/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Uncontrolled resource consumption SNYK-JS-BRACES-6838727	696
	Inefficient Regular Expression Complexity SNYK-JS-MICROMATCH-6838728	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:

🦉 Uncontrolled resource consumption

---

Description

• Upgrade @testing-library/jest-dom from version 5.17.0 to 6.0.0 to address high severity vulnerabilities.
• The vulnerabilities fixed are Uncontrolled resource consumption and Inefficient Regular Expression Complexity.
• The changes affect package.json and package-lock.json in the example directory.

---

Changes walkthrough

Relevant files

Dependencies

package.json Upgrade Dependency to Resolve Vulnerabilities                                    example/package.json Upgrade @testing-library/jest-dom from 5.17.0 to 6.0.0 to fix vulnerabilities. +1/-1      package-lock.json Update package-lock.json for Dependency Upgrade                                example/package-lock.json Update package-lock.json with the new version of @testing-library/jest-dom. +6498/-1377

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai]

Things to consider

Based on the information provided and the PR Git Diff for the example/package.json, there are no direct indications of functional bugs, regression bugs, or missed edge cases introduced by this PR. The PR is a dependency upgrade for @testing-library/jest-dom from version 5.17.0 to 6.0.0. Here are some considerations:

1. Major Version Upgrade: Since the upgrade is from version 5 to 6, this is a major version change which could include breaking changes. It's important to review the release notes of @testing-library/jest-dom for any breaking changes that might affect the current test suite.

2. Peer Dependencies: If @testing-library/jest-dom has peer dependencies, there might be a need to upgrade those as well to ensure compatibility with the new version. This PR does not show changes to any other dependencies, so if there are required peer dependency upgrades, they might be missing.

3. Test Suite Compatibility: The upgrade might introduce changes that are incompatible with the current test suite. It's essential to run the entire test suite to ensure that all tests pass with the new version of the library.

Without additional context or the ability to run tests and check for compatibility issues, it's not possible to definitively list bugs. However, the points above are critical areas to consider when upgrading a major dependency version to prevent potential bugs or issues.