[Snyk] Upgrade @emotion/react from 11.7.0 to 11.11.1 #2452
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade @emotion/react from 11.7.0 to 11.11.1.
ℹ️ 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.
The recommended version fixes:
SNYK-JS-BABELTRAVERSE-5962462
Why? Currently trending on Twitter, Recently disclosed, CVSS 9.3
(*) Note that the real score may have changed since the PR was raised.
Release notes
Package name: @emotion/react
Patch Changes
9357f337
Thanks @ naari3! - AddedElementType
to the Emotion'sJSX
namespace. It's defined in the same way as the one in@ types/react
and should make it possible to use components that returnstring
s,Promise
s and other types that are valid in React.Minor Changes
336f3d50
Thanks @ Andarist! - Added support for cascade@ layer
s by updating the underlying parser (stylis).Patch Changes
#3029
eed5e6cf
Thanks @ Andarist! - Fixed importing in Node ESMUpdated dependencies [
336f3d50
,eed5e6cf
]: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
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs