Bump eventsource and nwb

[dependabot[bot]]

Bumps eventsource to 1.1.2 and updates ancestor dependency nwb. These dependencies need to be updated together.

Updates eventsource from 0.1.6 to 1.1.2

Changelog

Sourced from eventsource's changelog.

1.1.2

• Inline origin resolution, drops original dependency (#281 Espen Hovlandsdal)

1.1.1

• Do not include authorization and cookie headers on redirect to different origin (#273 Espen Hovlandsdal)

1.1.0

• Improve performance for large messages across many chunks (#130 Trent Willis)
• Add createConnection option for http or https requests (#120 Vasily Lavrov)
• Support HTTP 302 redirects (#116 Ryan Bonte)
• Prevent sequential errors from attempting multiple reconnections (#125 David Patty)
• Add new to correct test (#111 Stéphane Alnet)
• Fix reconnections attempts now happen more than once (#136 Icy Fish)

1.0.7

• Add dispatchEvent to EventSource (#101 Ali Afroozeh)
• Added checkServerIdentity option (#104 cintolas)
• Surface request error message (#107 RasPhilCo)

1.0.6

• Fix issue where a unicode sequence split in two chunks would lead to invalid messages (#108 Espen Hovlandsdal)
• Change example to use eventsource/ssestream (Aslak Hellesøy)

1.0.5

• Check for window existing before polyfilling. (#80 Neftaly Hernandez)

1.0.4

• Pass withCredentials on to the XHR. (#79 Ken Mayer)

1.0.2

• Fix proxy not working when proxy and target URL uses different protocols. (#76 Espen Hovlandsdal)
• Make close() a prototype method instead of an instance method. (#77 Espen Hovlandsdal)

1.0.1

• Reconnect if server responds with HTTP 500, 502, 503 or 504. (#74 Vykintas Narmontas)

1.0.0

• Add missing removeEventListener-method. (#51 Yucheng Tu / Espen Hovlandsdal)
• Fix EventSource reconnecting on non-200 responses. (af84476 Espen Hovlandsdal)
• Add ability to customize https options. (#53 Rafael Alfaro)

... (truncated)

Commits

• 0a8b85b 1.1.2
• f99ae66 docs: update history for 1.1.2
• 06c9721 chore: rebuild polyfill
• 9494642 fix: inline origin resolution, drop original dependency (#281)
• aa7a408 1.1.1
• 56d489e chore: rebuild polyfill
• 4a951e5 docs: update history for 1.1.1
• f9f6416 fix: strip sensitive headers on redirect to different origin
• 9dd0687 1.1.0
• 49497ba Update history for 1.1.0 (#146)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by rexxars, a new releaser for eventsource since your current version.

Updates nwb from 0.22.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/unlayer/react-email-editor/network/alerts).

[dependabot[bot]]

Looks like these dependencies are no longer a dependency, so this is no longer needed.