#327077d930d 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.
#327077d930d 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.
#3198d8ff8a5 Thanks @Andarist! - Migrated away from relying on process.env.NODE_ENV checks to differentiate between production and development builds.
Development builds (and other environment-specific builds) can be used by using proper conditions (see here). Most modern bundlers/frameworks already preconfigure those for the user so no action has to be taken.
Default files should continue to work in all environments.
#255885772c3 Thanks @emmatown! - 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
#255885772c3 Thanks @emmatown! - Fixed options parameter to createEmotion from @emotion/css/create-instance incorrectly being marked as optional when it's required.
#327077d930d 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.
#3198d8ff8a5 Thanks @Andarist! - Migrated away from relying on process.env.NODE_ENV checks to differentiate between production and development builds.
Development builds (and other environment-specific builds) can be used by using proper conditions (see here). Most modern bundlers/frameworks already preconfigure those for the user so no action has to be taken.
Default files should continue to work in all environments.
#3215a9f6912 Thanks @Andarist! - Added edge-light and workerd conditions to package.json manifest to better serve users using Vercel Edge and Cloudflare Workers.
#281565a1eea Thanks @srmagura! - Automatic labeling at runtime is now an opt-in feature. Define globalThis.EMOTION_RUNTIME_AUTO_LABEL = true before Emotion gets initialized to enable it.
Patch Changes
#3206d1994c4 Thanks @DiegoAndai! - Improved compatibility with the upcoming @types/react for React 19 where the global JSX namespace doesn't exist anymore
#320856109e7 Thanks @Andarist! - Only forward defined refs to improve compatibility with the upcoming React 19
#327077d930d 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.
#3198d8ff8a5 Thanks @Andarist! - Migrated away from relying on process.env.NODE_ENV checks to differentiate between production and development builds.
Development builds (and other environment-specific builds) can be used by using proper conditions (see here). Most modern bundlers/frameworks already preconfigure those for the user so no action has to be taken.
Default files should continue to work in all environments.
#3215a9f6912 Thanks @Andarist! - Added edge-light and workerd conditions to package.json manifest to better serve users using Vercel Edge and Cloudflare Workers.
#3206d1994c4 Thanks @DiegoAndai! - Improved compatibility with the upcoming @types/react for React 19 where the global JSX namespace doesn't exist anymore
#320856109e7 Thanks @Andarist! - Only forward defined refs to improve compatibility with the upcoming React 19
Most Recent Ignore Conditions Applied to This Pull Request
| Dependency Name | Ignore Conditions |
| --- | --- |
| @emotion/styled | [>= 11.9.a, < 11.10] |
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 show ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
- `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
- `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency
- `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
Bumps the emotion-dependencies group with 4 updates in the / directory: @emotion/babel-plugin, @emotion/css, @emotion/react and @emotion/styled.
Updates
@emotion/babel-pluginfrom 11.11.0 to 11.13.5Release notes
Sourced from
@emotion/babel-plugin's releases.Commits
c161e6fVersion Packages (#3272)f45eb19Update changeset (#3273)77d930dFix inconsistent hashes using development vs production bundles/exportscon...e310c6eVersion Packages (#3263)b10de75FixCannot find name 'EmotionCache'type error (#3262)31fa40bVersion Packages (#3247)532ff57Add fetchpriority to props (#3093)ad630e3Minor performance improvements (#3244)3f46884Version Packages (#3235)153cf88Add scale property as unitless (#3240)Updates
@emotion/cssfrom 11.11.2 to 11.13.5Release notes
Sourced from
@emotion/css's releases.Commits
c161e6fVersion Packages (#3272)f45eb19Update changeset (#3273)77d930dFix inconsistent hashes using development vs production bundles/exportscon...e310c6eVersion Packages (#3263)b10de75FixCannot find name 'EmotionCache'type error (#3262)31fa40bVersion Packages (#3247)532ff57Add fetchpriority to props (#3093)ad630e3Minor performance improvements (#3244)3f46884Version Packages (#3235)153cf88Add scale property as unitless (#3240)Updates
@emotion/reactfrom 11.11.3 to 11.13.5Release notes
Sourced from
@emotion/react's releases.... (truncated)
Commits
c161e6fVersion Packages (#3272)f45eb19Update changeset (#3273)77d930dFix inconsistent hashes using development vs production bundles/exportscon...e310c6eVersion Packages (#3263)b10de75FixCannot find name 'EmotionCache'type error (#3262)31fa40bVersion Packages (#3247)532ff57Add fetchpriority to props (#3093)ad630e3Minor performance improvements (#3244)3f46884Version Packages (#3235)153cf88Add scale property as unitless (#3240)Updates
@emotion/styledfrom 11.11.0 to 11.13.5Release notes
Sourced from
@emotion/styled's releases.Commits
c161e6fVersion Packages (#3272)f45eb19Update changeset (#3273)77d930dFix inconsistent hashes using development vs production bundles/exportscon...e310c6eVersion Packages (#3263)b10de75FixCannot find name 'EmotionCache'type error (#3262)31fa40bVersion Packages (#3247)532ff57Add fetchpriority to props (#3093)ad630e3Minor performance improvements (#3244)3f46884Version Packages (#3235)153cf88Add scale property as unitless (#3240)Most Recent Ignore Conditions Applied to This Pull Request
| Dependency Name | Ignore Conditions | | --- | --- | | @emotion/styled | [>= 11.9.a, < 11.10] |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 show