Bump engine.io and nwb

[dependabot[bot]]

Bumps engine.io to 3.6.1 and updates ancestor dependency nwb. These dependencies need to be updated together.

Updates engine.io from 3.1.5 to 3.6.1

Release notes

Sourced from engine.io's releases.

3.6.1

:warning: This release contains an important security fix :warning:

A malicious client could send a specially crafted HTTP request, triggering an uncaught exception and killing the Node.js process:

Error: read ECONNRESET
    at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (internal/streams/destroy.js:106:8)
    at emitErrorCloseNT (internal/streams/destroy.js:74:3)
    at processTicksAndRejections (internal/process/task_queues.js:80:21) {
  errno: -104,
  code: 'ECONNRESET',
  syscall: 'read'
}

Please upgrade as soon as possible.

Bug Fixes

• catch errors when destroying invalid upgrades (83c4071)

3.6.0

Bug Fixes

• add extension in the package.json main entry (#608) (3ad0567)
• do not reset the ping timer after upgrade (1f5d469)

Features

• decrease the default value of maxHttpBufferSize (58e274c)

This change reduces the default value from 100 mb to a more sane 1 mb.

This helps protect the server against denial of service attacks by malicious clients sending huge amounts of data.

See also: https://github.com/advisories/GHSA-j4f2-536g-r55m

• increase the default value of pingTimeout (f55a79a)

Links

• Diff: https://github.com/socketio/engine.io/compare/3.5.0...3.6.0
• Client release: -

... (truncated)

Changelog

Sourced from engine.io's changelog.

3.6.1 (2022-11-20)

:warning: This release contains an important security fix :warning:

A malicious client could send a specially crafted HTTP request, triggering an uncaught exception and killing the Node.js process:

Error: read ECONNRESET
    at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (internal/streams/destroy.js:106:8)
    at emitErrorCloseNT (internal/streams/destroy.js:74:3)
    at processTicksAndRejections (internal/process/task_queues.js:80:21) {
  errno: -104,
  code: 'ECONNRESET',
  syscall: 'read'
}

Please upgrade as soon as possible.

Bug Fixes

• catch errors when destroying invalid upgrades (83c4071)

6.2.1 (2022-11-20)

:warning: This release contains an important security fix :warning:

A malicious client could send a specially crafted HTTP request, triggering an uncaught exception and killing the Node.js process:

Error: read ECONNRESET
    at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (internal/streams/destroy.js:106:8)
    at emitErrorCloseNT (internal/streams/destroy.js:74:3)
    at processTicksAndRejections (internal/process/task_queues.js:80:21) {
  errno: -104,
  code: 'ECONNRESET',
  syscall: 'read'
}

Please upgrade as soon as possible.

Bug Fixes

... (truncated)

Commits

• 67a3a87 chore(release): 3.6.1
• 83c4071 fix: catch errors when destroying invalid upgrades
• f62f265 chore(release): 3.6.0
• f55a79a feat: increase the default value of pingTimeout
• 1f5d469 fix: do not reset the ping timer after upgrade
• 3ad0567 fix: add extension in the package.json main entry (#608)
• 58e274c feat: decrease the default value of maxHttpBufferSize
• b9dee7b chore(release): 3.5.0
• 19cc582 feat: add support for all cookie options
• 5ad2736 feat: disable perMessageDeflate by default
• Additional commits viewable in compare view

Updates nwb from 0.23.0 to 0.25.2

Release notes

Sourced from nwb's releases.

v0.25.2

Fixed

• Bumped Node.js version in templates.

v0.25.1

Changed

• Don't include docs/ in the npm package.

v0.25.0

Breaking Changes

• Node.js 8 is no longer supported; Node.js 10.13.0 is now the minimum required version, as per many of nwb's dependencies.

Browser Support

• Removed default polyfills for Promise, fetch() and Object.assign() and deprecated polyfill config.

  If you need to support older browsers, you will now need to include the necessary polyfills in your app - see the new Browser Support docs for details on polyfilling and suggested modules which provide them.

  If this change affects your app, a quick fix is to use react-app-polyfill's IE11 polyfill, which is equivalent to what nwb's default polyfill used to be:

  import 'react-app-polyfill/ie11'
  

• For apps and quick commands, @babel/preset-env is now configured to only transpile the necessary ECMAScript 2015+ for supported browsers.

  When running a development server, this defaults to the most recent version of Chrome, Firefox or Safari, so you may need to adjust browsers.development config if you're using an out of date browser and you will need to adjust it if you're developing with an older browser supported by your app.

• Default browser configuration for Autoprefixer when building an app has changed from >1%, last 4 versions, Firefox ESR, not ie < 9 to >0.2%, not dead, not op_mini all.

  When running a development server, the default browser configuration has changed to last 1 chrome version, last 1 firefox version, last 1 safari version.

Configuration

• Deprecated using a string for webpack.autoprefixer config to configure supported browsers - this will no longer do anything and should be moved to the new browsers config.

• Removed support for babel.stage and webpack.uglify config deprecated in nwb v0.24.0.

• copy-webpack-plugin v6.0.0 has breaking changes to its options which you should read if you're using webpack.copy config.

  In particular, the ignore option in a copy pattern must now be put inside the new globOptions option.

Dependencies

• file-loader v6.0.0 changed its default hashing algorithm so hashes in output filenames will change after updating to this release, even if their contents haven't changed.

Added

• Added top-level browsers config to configure supported browsers. This supports using separate browserslist queries for development and production.

... (truncated)

Changelog

Sourced from nwb's changelog.

0.25.2 / 2020-05-20

Fixed

• Bumped Node.js version in templates.

0.25.1 / 2020-05-20

Changed

• Don't include docs/ in the npm package.

0.25.0 / 2020-05-20

Breaking Changes

• Node.js 8 is no longer supported; Node.js 10.13.0 is now the minimum required version, as per many of nwb's dependencies.

Browser Support

• Removed default polyfills for Promise, fetch() and Object.assign() and deprecated polyfill config.

  If you need to support older browsers, you will now need to include the necessary polyfills in your app - see the new Browser Support docs for details on polyfilling and suggested modules it's to provide them.

  If this change affects your app, a quick fix is to use react-app-polyfill's IE11 polyfill, which is equivalent to what nwb's default polyfill used to be:

  import 'react-app-polyfill/ie11'
  

• For apps and quick commands, @babel/preset-env is now configured to only transpile the necessary ECMAScript 2015+ for supported browsers.

  When running a development server, this defaults to the most recent version of Chrome, Firefox or Safari, so you may need to adjust browsers.development config if you're using an out of date browser and you will need to adjust it if you're developing with an older browser supported by your app.

• Default browser configuration for Autoprefixer when building an app has changed from >1%, last 4 versions, Firefox ESR, not ie < 9 to >0.2%, not dead, not op_mini all.

  When running a development server, the default browser configuration has changed to last 1 chrome version, last 1 firefox version, last 1 safari version.

Configuration

• Deprecated using a string for webpack.autoprefixer config to configure supported browsers - this will no longer do anything and should be moved to the new browsers config.

• Removed support for babel.stage and webpack.uglify config deprecated in nwb v0.24.0.

• copy-webpack-plugin v6.0.0 has breaking changes to its options which you should read if you're using webpack.copy config.

  In particular, the ignore option in a copy pattern must now be put inside the new globOptions option.

Dependencies

• file-loader v6.0.0 changed its default hashing algorithm so hashes in output filenames will change after updating to this release, even if their contents haven't changed.

... (truncated)

Commits

• 8963342 Release v0.25.2
• 24f77a3 Bump Node.js version in templates
• afe6dd1 Release v0.25.1
• 7b50e35 Release v0.25.0
• 2f71b69 Update dependencies
• 3a5fde7 Move changes from 2+ majorish releses ago to an archive file
• 524a642 Add targets config for preset-env
• d028177 Update dependencies
• c8e9dbf Added top-level browsers config for configuring browser support with a browse...
• bf05318 Breaking: Drop support for Node.js 8 - Node.js 10.13.0 is now the minimum req...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/bilal114/react-date-range-calendar/network/alerts).