[Snyk] Upgrade @emotion/css from 11.10.0 to 11.13.5 #1708
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Snyk has created this PR to upgrade @emotion/css from 11.10.0 to 11.13.5. See this package in npm: @emotion/css See this project in Snyk: https://app.snyk.io/org/sammyfilly/project/f5b99248-06f5-49bd-9bd1-def4b50c0206?utm_source=github&utm_medium=referral&page=upgrade-pr
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Deployment failed with the following error: |
|
|
Reviewer's Guide by SourceryThis PR updates the @emotion/css dependency from version 11.10.0 to 11.13.5 in the project's package.json. The update includes several minor version bumps and patches, with the most notable fix addressing inconsistent hashes when using development vs production bundles with source maps enabled. No diagrams generated as the changes look simple and do not need a visual representation. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
We have skipped reviewing this pull request. Here's why:
- It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
- We don't review packaging changes - Let us know if you'd like us to change this.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Snyk has created this PR to upgrade @emotion/css from 11.10.0 to 11.13.5.
ℹ️ 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 is 9 versions ahead of your current version.
The recommended version was released on 22 days ago.
Release notes
Package name: @emotion/css
-
11.13.5 - 2024-11-20
-
-
- @ emotion/[email protected]
- @ emotion/[email protected]
- @ emotion/[email protected]
-
11.13.4 - 2024-10-01
-
11.13.0 - 2024-07-20
-
11.12.0 - 2024-07-19
-
11.11.2 - 2023-06-16
-
11.11.0 - 2023-05-06
-
11.10.8 - 2023-04-28
-
11.10.6 - 2023-02-16
-
11.10.5 - 2022-10-27
-
11.10.0 - 2022-07-31
from @emotion/css GitHub release notesPatch Changes
#3270
77d930dThanks @ emmatown! - Fix inconsistent hashes using development vs production bundles/exportsconditions when using@ emotion/babel-pluginwithsourceMap: true(the default). This is particularly visible when using Emotion with the Next.js Pages router where thedevelopmentcondition is used when bundling code but not when importing external code with Node.js.Updated dependencies [
77d930d]:Important
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:
Summary by Sourcery
Build: