Sourced from @emotion/react
's
releases.
@emotion/react
@11
.13.0Minor Changes
#3198
d8ff8a5
Thanks@Andarist
! - Migrated away from relying onprocess.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.
#3215
a9f6912
Thanks@Andarist
! - Addededge-light
andworkerd
conditions topackage.json
manifest to better serve users using Vercel Edge and Cloudflare Workers.Patch Changes
@emotion/react
@11
.12.0Minor Changes
- #2815
65a1eea
Thanks@srmagura
! - Automatic labeling at runtime is now an opt-in feature. DefineglobalThis.EMOTION_RUNTIME_AUTO_LABEL = true
before Emotion gets initialized to enable it.Patch Changes
#3206
d1994c4
Thanks@DiegoAndai
! - Improved compatibility with the upcoming@types/react
for React 19 where the globalJSX
namespace doesn't exist anymore#3208
56109e7
Thanks@Andarist
! - Only forward definedref
s to improve compatibility with the upcoming React 19
70ad1d3
Version Packages (#3214)a9f6912
Added edge-light
and workerd
conditions (#3215)d8ff8a5
Update Preconstruct and use import conditions (#3198)d57cfcb
Version Packages (#3188)d1994c4
Improved compatibility with the upcoming @types/react
for
React 19 (#3206)56109e7
Only forward defined ref
s (#3208)de80631
Update Changesets (#3207)4cc565f
Update Jest dependencies (#3199)b4da6d3
Update TypeScript, ESLint and Prettier (#3200)65a1eea
Make runtime label extraction opt-in (#2815)