Important: This documentation covers Yarn 1 (Classic).
For Yarn 2+ docs and migration guide, see yarnpkg.com.

Package detail

@emotion/core

emotion-js8.2mMIT11.0.0TypeScript support: included

null

readme

changelog

@emotion/core

11.0.0

Major Changes

  • b8476e08 #1675 Thanks @mitchellhamilton! - Rename @emotion/core to @emotion/react. Please change any imports of @emotion/core to import @emotion/react or use the @emotion/pkg-renaming ESLint rule from @emotion/eslint-plugin.

11.0.0-rc.0

Major Changes

11.0.0-next.10

Major Changes

  • b8476e08 #1600 Thanks @mitchellhamilton! - Rename @emotion/core to @emotion/react. Please change any imports of @emotion/core to import @emotion/react or use the @emotion/pkg-renaming ESLint rule from @emotion/eslint-plugin.

11.0.0-next.9

Patch Changes

11.0.0-next.8

Major Changes

  • c643107 #1600 Thanks @joltmode! - Reworked TypeScript definitions so it's easier to provide a type for Theme. Instead of creating custom instances (like before) you can augment builtin Theme interface like this:

    declare module '@emotion/core' {
      export interface Theme {
        primaryColor: string
        secondaryColor: string
      }
    }

Minor Changes

  • c643107 #1600 Thanks @joltmode! - Support functions in arrays passed to css prop and Global's styles prop. This allows for composition of theme-accepting functions.

Patch Changes

11.0.0-next.7

Patch Changes

11.0.0-next.6

Major Changes

  • 843bfb11 #1600 Thanks @Andarist! - Removed @emotion/css - it's main purpose was to allow css to be a Babel macro, but since babel-plugin-macros allows us to keep imports nowadays this is no longer needed. @emotion/core/macro has been added to account for this use case and appropriate changes has been made to babel-plugin-emotion to facilitate those changes.

    If you have used @emotion/css directly (it was always reexported from @emotion/core) or you have been using its macro then you should update your code like this:

    -import css from '@emotion/css'
    +import { css } from '@emotion/core'
    
    // or
    -import css from '@emotion/css/macro'
    +import { css } from '@emotion/core/macro'
  • cbb8b796 #1600 Thanks @Andarist! - emotion-theming has been removed and all its exports were moved to @emotion/core package. Please import them like this import { useTheme, ThemeProvider, withTheme } from '@emotion/core' from now on.

Minor Changes

  • 828111cd #1600 Thanks @Andarist! - Global imported from macro entry (@emotion/core/macro) gets source maps generated now when inline css-less expression is used as value of the styles prop.

Patch Changes

11.0.0-next.5

Patch Changes

11.0.0-next.4

Patch Changes

11.0.0-next.3

Patch Changes

11.0.0-next.2

Major Changes

Patch Changes

11.0.0-next.1

Patch Changes

11.0.0-next.0

Major Changes

  • 302bdba1 #1600 Thanks @mitchellhamilton! - Ensure packages are major bumped so that pre-release versions of the linked packages are consistent in the major number

Patch Changes

10.1.1

Patch Changes

  • fe30cbd6 #2066 Thanks @Andarist! - Fixed an issue with React giving warning about static children not having unique keys when using the classic jsx factory. This example illustrates the situation in which this has been incorrectly happening:

    <div css={{ color: 'hotpink' }}>
      <div />
      <div />
    </div>

10.1.0

Minor Changes

  • 71514b06 #1970 Thanks @FLGMwt! - Support for the new JSX runtimes has been added. They require compatible React versions and shouldn't be manually used.

    To use them you can use the new @jsxImportSource @emotion/core pragma instead of the old @jsx jsx or you can use @emotion/babel-preset-css-prop with { runtime: 'automatic' } option to have it handled automatically for you for the whole project.

10.0.35

Patch Changes

  • 2cf3b16b #1973 Thanks @santialbo! - Fixed label extraction from the stack traces in node for components wrapped in React.forwardRef. This has affected only development builds.

10.0.34

Patch Changes

  • 4979ebb2 #1966 Thanks @chnakamura! - Fixed label extraction from the stack traces in Chrome in certain scenarios. This has affected only development builds.

10.0.28

Patch Changes

  • d0b2a94 #1714 Thanks @Andarist! - Fixed label extraction from the stack traces in FireFox and Safari. We have failed to match a label in Emotion wrappers like Theme UI which caused SSR mismatches in mentioned browsers. This has affected only development builds.

10.0.27

Patch Changes

10.0.22

Patch Changes

10.0.21

Patch Changes

  • 7855db4a #1537 Thanks @Andarist! - Add missing /* #__PURE__ */ annotation to creation of EmotionCssPropInternal

10.0.20

Patch Changes

  • 38bb2b19 #1530 Thanks @Andarist! - Fix class not being applied when putting nil as css prop value on wrapper component

10.0.17

Patch Changes

10.0.16

Patch Changes

  • 47262b64 - Fix labels from stack traces in some cases

10.0.15

Patch Changes

10.0.14

Patch Changes