Skip to content

Conversation

@graymalkin77
Copy link

snyk-top-banner

Snyk has created this PR to upgrade @emotion/react from 11.10.5 to 11.14.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.


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

  • The recommended version was released 8 months ago.

Release notes
Package name: @emotion/react
  • 11.14.0 - 2024-12-09

    Minor Changes

    • #3284 a19d019 Thanks @ Andarist! - Source code has been migrated to TypeScript. From now on type declarations will be emitted based on that, instead of being hand-written.

    Patch Changes

  • 11.13.5 - 2024-11-20

    Patch Changes

    • #3270 77d930d Thanks @ emmatown! - Fix inconsistent hashes using development vs production bundles/exports conditions when using @ emotion/babel-plugin with sourceMap: true (the default). This is particularly visible when using Emotion with the Next.js Pages router where the development condition is used when bundling code but not when importing external code with Node.js.

    • Updated dependencies [77d930d]:

  • 11.13.3 - 2024-08-21
  • 11.13.0 - 2024-07-20
  • 11.12.0 - 2024-07-19
  • 11.11.4 - 2024-02-27
  • 11.11.3 - 2023-12-23
  • 11.11.1 - 2023-06-07
  • 11.11.0 - 2023-05-06
  • 11.10.8 - 2023-04-28
  • 11.10.6 - 2023-02-16
  • 11.10.5 - 2022-10-27
from @emotion/react GitHub release notes

Important

  • 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:

Snyk has created this PR to upgrade @emotion/react from 11.10.5 to 11.14.0.

See this package in npm:
@emotion/react

See this project in Snyk:
https://app.snyk.io/org/cognigy-gmbh/project/9925025e-9fa9-4575-b30a-373ebb7ce44d?utm_source=github&utm_medium=referral&page=upgrade-pr
Copilot AI review requested due to automatic review settings August 15, 2025 17:05
@graymalkin77
Copy link
Author

graymalkin77 commented Aug 15, 2025

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

license/snyk check is complete. No issues have been found. (View Details)

code/snyk check is complete. No issues have been found. (View Details)

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR upgrades the @emotion/react dependency from version 11.10.5 to 11.14.0, bringing the project up to date with the latest version that includes TypeScript migration and various bug fixes.

  • Updates @emotion/react from 11.10.5 to 11.14.0 (11 versions ahead)
  • Incorporates improvements including TypeScript migration and hash consistency fixes
  • Maintains compatibility as this is a minor version upgrade

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

"@cognigy/socket-client": "^4.9.2",
"@emotion/cache": "^10.0.29",
"@emotion/react": "^11.7.1",
"@emotion/react": "^11.14.0",
Copy link

Copilot AI Aug 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The package.json shows the current version as ^11.7.1 in the diff, but the PR description indicates upgrading from 11.10.5 to 11.14.0. This inconsistency suggests the package.json may not reflect the actual installed version or there's a mismatch in the upgrade scope.

Suggested change
"@emotion/react": "^11.14.0",
"@emotion/react": "^11.10.5",

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants