[Snyk] Fix for 1 vulnerabilities

[ekmixon]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • grid-packages/ag-grid-react/package.json

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	696/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 7.5	Regular Expression Denial of Service (ReDoS) SNYK-JS-ANSIREGEX-1583908	Yes	Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: html-webpack-plugin

The new version differs by 106 commits.

• 873d75b chore(release): 5.5.0
• ddeb774 chore: update examples
• 1e42625 feat: Support type=module via scriptLoading option
• 7d3645b Bump pretty-error to 4.0.0 to fix transitive vuln for ansi-regex CVE-2021-3807
• 79be779 [chore] changes actions to run on pull_requests
• b7e5859 [chore] fixes CI to avoid race conditions
• 48131d3 chore(release): 5.4.0
• 16a841a [chore] rebuild examples
• 3bb7c17 Update index.js
• e38ac97 Update index.js
• f08bd02 [chore] updates fixtures
• d62a10f [chore] upgrades html-minifier-terser@5.0.0 -> 6.0.2
• 2f5de7a Remove archived plugin
• 8f8f7c5 chore(release): 5.3.2
• 053c6e6 chore: update snapshot tests for webpack 5.4.0
• 9c7fba0 Fix security vulnerabilities
• b98fbeb Fix security vulnerabilities
• 25cdfc7 Added inject-body-webpack-plugin to readme
• 0e4c1fb Update README to document actual behavior
• 0a6568d chore(release): 5.3.1
• 82d0ee8 fix: remove loader-utils from plugin core
• 6f39192 chore(release): 5.3.0
• d654f5b feat: allow to modify the interpolation options in webpack config
• 41d7a50 feat: drop loader-utils dependency

See the full diff

Package name: webpack-dev-server

The new version differs by 250 commits.

• c9271b9 chore(release): 4.0.0
• 18bf369 test: fix stability (Excel Export Line Number and Column Alphabets font size is bigger ag-grid/ag-grid#3676)
• cdcabb2 fix: respect protocol from browser for manual setup (Support Column flex to fill the entire available space even after it was moved or swapped ag-grid/ag-grid#3675)
• 1768d6b fix: initial reloading for lazy compilation (suppressCount does not work when groupUseEntireRow = true ag-grid/ag-grid#3662)
• 4f5bab1 docs: improve examples (ag-grid export as CSV is displaying [object object] in csv file but loads good in table. ag-grid/ag-grid#3672)
• f2d87fb fix: improve https CLI output (ag-grid-angular cell value not binding automatically ag-grid/ag-grid#3673)
• 0277c5e chore: remove redundant console statements (Question: When can we find Ag Grid's Next Release Date? ag-grid/ag-grid#3671)
• 16fcdbc docs: add `ipc` example (Fix NPE when using row group edit ag-grid/ag-grid#3667)
• 8915fb8 test: add e2e tests for built in routes (Column flex issue - jumps/glitches on official examples ag-grid/ag-grid#3669)
• 4d1cbe1 docs: ask `version` information in issue template (Is it possible to style the dragged element of the columns? ag-grid/ag-grid#3668)
• b6c1881 chore(deps-dev): bump core-js from 3.16.1 to 3.16.2 (Some column events can't be bound with column definitions ag-grid/ag-grid#3666)
• ffa8cc5 chore(deps-dev): bump supertest from 6.1.5 to 6.1.6 (tool panel performance issue in IE 11 ag-grid/ag-grid#3665)
• f1fdaa7 chore(release): 4.0.0-rc.1
• c4678bc fix: legacy API (Tree data aggregate column set filter not working ag-grid/ag-grid#3660)
• d8bdd03 test: fix stability (ag-grid-enteprise with noImplicitAny: Could not find a declaration file for module  ag-grid/ag-grid#3661)
• 22b1414 refactor: remove `killable` (Missing exports for /filter/provided ag-grid/ag-grid#3657)
• 75bafbf test: add e2e tests for module federation (Comparator not responding in ag-grid ag-grid/ag-grid#3658)
• 493ccbd chore(deps): update `ws` ("agSetColumnFilter" breaks application  ag-grid/ag-grid#3652)
• ae8c523 test: add e2e test for universal compiler (enableCellTextSelection does not exist on 'GridOptions' ag-grid/ag-grid#3656)
• f94b84f chore(deps): update (Allow navigating to non-editable cell by tab when editing=true ag-grid/ag-grid#3655)
• 1923132 test: fix cli
• 2adfd01 test: fix todo (When switching themes dynamically icons are not displaying ag-grid/ag-grid#3653)
• 6e2cbde fix: proxy logging and allow to pass options without the `target` option (Context menu enhancement ag-grid/ag-grid#3651)
• c9ccc96 fix: respect infastructureLogging.level for client.logging (Export Data As Excel - Turn on Filter in Excel ag-grid/ag-grid#3613)

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

---

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

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[pull-request-quantifier-deprecated]

This PR has 4 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +2 -2
Percentile : 1.6%

Total files changed: 1

Change summary by file extension:
.json : +2 -2

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.