[Snyk] Security upgrade engine.io from 4.0.0 to 4.1.2

[snyk-bot]

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:
  • examples/latency/package.json

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	661/1000 Why? Recently disclosed, Has a fix available, CVSS 7.5	Uncaught Exception SNYK-JS-ENGINEIO-2336356	No	No Known Exploit

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

Commit messages

Package name: engine.io

The new version differs by 30 commits.

• c6315af chore(release): 4.1.2
• a70800d fix: properly handle invalid data sent by a malicious websocket client
• 9534355 chore(release): 4.1.1
• ae840fa chore: point towards the master branch for the CI badge
• ff2b8ab fix: do not reset the ping timer after upgrade
• e5b307c chore(release): 4.1.0
• 663d326 feat: add support for v3.x clients
• 9b62152 chore(release): 4.0.6
• 5a91253 chore: bump ws and debug versions
• fffa0a3 chore: update GitHub issue templates
• cec2750 fix: correctly pass the options when using the Server constructor (fix: correctly pass the options when using the Server constructor socketio/engine.io#610)
• 04ea358 docs(changelog): include changelog for release 3.5.0
• e7115b8 chore(release): 4.0.5
• f5efa1e refactor: use ES6 syntax for the tests
• 312bd35 ci: migrate to GitHub Actions
• c2981c6 chore(release): 4.0.4
• 67ca12c chore(release): 4.0.3
• 9ddccf3 chore: bump engine.io-client
• 16fd658 chore(release): 4.0.2
• 17b8c2f fix: add extension in the package.json main entry (package.json main entry missing extension socketio/engine.io#608)
• 3284208 chore: bump engine.io-client
• 58943c3 chore(release): 4.0.1
• c099338 refactor: remove binary handling for the polling transport
• fe093ba fix: do not overwrite CORS headers upon error

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

[pull-request-quantifier-deprecated]

This PR has 2 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       : +1 -1
Percentile : 0.8%

Total files changed: 1

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

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.