Releases: emotion-js/emotion
@emotion/cache@11.13.1
@emotion/utils@1.4.0
Minor 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.
@emotion/use-insertion-effect-with-fallbacks@1.1.0
Minor 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.
@emotion/styled@11.13.0
Minor 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/sheet@1.4.0
Minor 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.
@emotion/serialize@1.3.0
Minor 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.
Patch Changes
@emotion/react@11.13.0
Minor 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/primitives@11.13.0
@emotion/primitives-core@11.13.0
Minor 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.