[Snyk] Upgrade emotion from 9.2.12 to 11.0.0

[Dargon789]

Snyk has created this PR to upgrade emotion from 9.2.12 to 11.0.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

• The recommended version is 36 versions ahead of your current version.

• The recommended version was released 4 years ago.

---

Important

• Warning: This PR contains a major version upgrade, and may be a breaking change.
• Check the changes in this PR to ensure they won't cause issues with your project.
• 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 upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Summary by Sourcery

Chores:

• Upgrade emotion from 9.2.12 to 11.0.0

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request upgrades the emotion dependency from version 9.2.12 to 11.0.0. The changes include updates to the package.json and yarn.lock files to reflect the new version.

Updated class diagram for emotion

classDiagram
  class Emotion {
    <<package>> emotion
    --
  }

  note for Emotion "Upgraded from 9.2.12 to 11.0.0"

Loading

File-Level Changes

Change	Details	Files
Upgraded the emotion dependency from version 9.2.10 to 11.0.0.	Updated the emotion dependency version in package.json. Updated the emotion dependency version in yarn.lock.	standalone-packages/sse-loading-screen/package.json standalone-packages/sse-loading-screen/yarn.lock

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@types/glob@5.0.35	None	0	5.9 kB	types
npm/@types/node@10.5.2	None	0	519 kB	types
npm/abab@1.0.4	None	0	11.1 kB	jeffcarp
npm/acorn-globals@4.1.0	None	0	8.26 kB	forbeslindesay
npm/acorn@5.7.1	None	0	564 kB	marijn
npm/ajv@5.5.2	eval	0	2.09 MB	esp
npm/align-text@0.1.4	None	0	8.83 kB	shinnn
npm/ansi-colors@1.1.0	None	0	22 kB	doowb
npm/ansi-gray@0.1.1	None	0	4.81 kB	jonschlinkert
npm/array-differ@1.0.0	None	0	1.45 kB	sindresorhus
npm/array-each@1.0.1	None	0	6.17 kB	jonschlinkert
npm/array-equal@1.0.0	None	0	2.05 kB	jongleberry
npm/array-slice@1.1.0	None	0	6.26 kB	jonschlinkert
npm/asn1@0.2.3	None	0	32.9 kB	pfmooney
npm/assert-plus@1.0.0	environment	0	11.4 kB	pfmooney
npm/async-limiter@1.0.0	None	0	53.8 kB	strml
npm/asynckit@0.4.0	None	0	27.4 kB	alexindigo
npm/atob@2.1.1	None	0	36.2 kB	coolaj86
npm/aws-sign2@0.7.0	None	0	14.2 kB	mikeal
npm/aws4@1.7.0	environment	0	31.9 kB	hichaelmart
npm/balanced-match@1.0.0	None	0	6.7 kB	juliangruber
npm/bcrypt-pbkdf@1.0.2	None	+1	203 kB	arekinath
npm/beeper@1.1.1	None	0	3.67 kB	sindresorhus

🚮 Removed packages: npm/clean-css@4.1.11, npm/deprecated@0.0.1, npm/duplexer@0.1.1, npm/event-stream@3.3.4, npm/from@0.1.7, npm/gulp-util@3.0.8, npm/gulp@3.9.1, npm/interpret@1.1.0, npm/map-stream@0.1.0, npm/pause-stream@0.0.11, npm/split@0.3.3, npm/stream-combiner@0.0.4

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
License Policy Violation	npm/bcrypt-pbkdf@1.0.2	License: BSD-3-Clause-HP - Not allowed by license policy (package/LICENSE)	standalone-packages/vscode-editor/yarn.lock	⚠︎
Deprecated	npm/abab@1.0.4	Reason: Use your platform's native atob() and btoa() methods instead	yarn.lock	⚠︎
License Policy Violation	npm/atob@2.1.1	License: CC-BY-3.0 - Not allowed by license policy (package/LICENSE.DOCS)	yarn.lock	⚠︎
High CVE	npm/acorn@5.7.1	CVE: GHSA-6chw-6frg-f759 Regular Expression Denial of Service in Acorn (HIGH) Affected versions: >= 5.5.0, < 5.7.4 Patched version: 5.7.4	yarn.lock	⚠︎

View full report↗︎

Next steps

What is a license policy violation?

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Find a package that does not violate your license policy or adjust your policy to allow this package's license.

What is a deprecated package?

The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.

Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution.

What is a CVE?

Contains a high severity Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/bcrypt-pbkdf@1.0.2
• @SocketSecurity ignore npm/abab@1.0.4
• @SocketSecurity ignore npm/atob@2.1.1
• @SocketSecurity ignore npm/acorn@5.7.1