Version Packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to next, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

next is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on next.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@emotion/css@11.0.0-next.1

Major Changes

• 1eaa3a38 #1600 Thanks @mitchellhamilton! - TypeScript types have been restructured. These changes:

  • Reduce build times when using emotion
  • In many cases remove the need for manually specifying generic parameters for your emotion components.

  If you encounter build issues after upgrade, try removing any manually specified generic types and let them be inferred. Otherwise refer to the breaking changes list below.

  Improvements

  • useTheme added to EmotionTheming interface and can now create your own closed variation of withTheme. More information in the docs under the theming section.
  • Union types as props are better supported and should be inferred properly
  • Build times should be reduced significantly in larger projects.

  Breaking changes

  • withTheme can now have the Theme type specified when calling it. For example withTheme<MyTheme>(MyComponent)

    Breaking change: Generic argument changed, if you were specifying the ComponentType you will need to remove the generic parameter. Recommend following example setup in the TypeScript docs under theming section

  • css function has been restricted to prevent passing of invalid types

  • CreateStyled functions no longer take a second ExtraProps argument. Instead move it to after the create styled call. For example

    styled<typeof MyComponent, ExtraProps>(MyComponent)({})
    to
    styled(MyComponent)<ExtraProps>({})

  • StyledComponent type no longer supports the third generic Theme parameter. Instead add the theme prop to the first Props argument. For example:

    StyledComponent<Props, {}, MyTheme>
    to
    StyledComponent<Props & { theme?: MyTheme }>

Patch Changes

• Updated dependencies [1eaa3a38]:
  • @emotion/serialize@1.0.0-next.0
  • babel-plugin-emotion@11.0.0-next.1

emotion-theming@11.0.0-next.1

Major Changes

• 1eaa3a38 #1600 Thanks @mitchellhamilton! - TypeScript types have been restructured. These changes:

  • Reduce build times when using emotion
  • In many cases remove the need for manually specifying generic parameters for your emotion components.

  If you encounter build issues after upgrade, try removing any manually specified generic types and let them be inferred. Otherwise refer to the breaking changes list below.

  Improvements

  • useTheme added to EmotionTheming interface and can now create your own closed variation of withTheme. More information in the docs under the theming section.
  • Union types as props are better supported and should be inferred properly
  • Build times should be reduced significantly in larger projects.

  Breaking changes

  • withTheme can now have the Theme type specified when calling it. For example withTheme<MyTheme>(MyComponent)

    Breaking change: Generic argument changed, if you were specifying the ComponentType you will need to remove the generic parameter. Recommend following example setup in the TypeScript docs under theming section

  • css function has been restricted to prevent passing of invalid types

  • CreateStyled functions no longer take a second ExtraProps argument. Instead move it to after the create styled call. For example

    styled<typeof MyComponent, ExtraProps>(MyComponent)({})
    to
    styled(MyComponent)<ExtraProps>({})

  • StyledComponent type no longer supports the third generic Theme parameter. Instead add the theme prop to the first Props argument. For example:

    StyledComponent<Props, {}, MyTheme>
    to
    StyledComponent<Props & { theme?: MyTheme }>

Patch Changes

• Updated dependencies [1eaa3a38, 22935470]:
  • @emotion/styled@11.0.0-next.1
  • @emotion/core@11.0.0-next.1

@emotion/serialize@1.0.0-next.0

Major Changes

• 1eaa3a38 #1600 Thanks @mitchellhamilton! - TypeScript types have been restructured. These changes:

  • Reduce build times when using emotion
  • In many cases remove the need for manually specifying generic parameters for your emotion components.

  If you encounter build issues after upgrade, try removing any manually specified generic types and let them be inferred. Otherwise refer to the breaking changes list below.

  Improvements

  • useTheme added to EmotionTheming interface and can now create your own closed variation of withTheme. More information in the docs under the theming section.
  • Union types as props are better supported and should be inferred properly
  • Build times should be reduced significantly in larger projects.

  Breaking changes

  • withTheme can now have the Theme type specified when calling it. For example withTheme<MyTheme>(MyComponent)

    Breaking change: Generic argument changed, if you were specifying the ComponentType you will need to remove the generic parameter. Recommend following example setup in the TypeScript docs under theming section

  • css function has been restricted to prevent passing of invalid types

  • CreateStyled functions no longer take a second ExtraProps argument. Instead move it to after the create styled call. For example

    styled<typeof MyComponent, ExtraProps>(MyComponent)({})
    to
    styled(MyComponent)<ExtraProps>({})

  • StyledComponent type no longer supports the third generic Theme parameter. Instead add the theme prop to the first Props argument. For example:

    StyledComponent<Props, {}, MyTheme>
    to
    StyledComponent<Props & { theme?: MyTheme }>

@emotion/styled-base@11.0.0-next.1

Major Changes

• 1eaa3a38 #1600 Thanks @mitchellhamilton! - TypeScript types have been restructured. These changes:

  • Reduce build times when using emotion
  • In many cases remove the need for manually specifying generic parameters for your emotion components.

  If you encounter build issues after upgrade, try removing any manually specified generic types and let them be inferred. Otherwise refer to the breaking changes list below.

  Improvements

  • useTheme added to EmotionTheming interface and can now create your own closed variation of withTheme. More information in the docs under the theming section.
  • Union types as props are better supported and should be inferred properly
  • Build times should be reduced significantly in larger projects.

  Breaking changes

  • withTheme can now have the Theme type specified when calling it. For example withTheme<MyTheme>(MyComponent)

    Breaking change: Generic argument changed, if you were specifying the ComponentType you will need to remove the generic parameter. Recommend following example setup in the TypeScript docs under theming section

  • css function has been restricted to prevent passing of invalid types

  • CreateStyled functions no longer take a second ExtraProps argument. Instead move it to after the create styled call. For example

    styled<typeof MyComponent, ExtraProps>(MyComponent)({})
    to
    styled(MyComponent)<ExtraProps>({})

  • StyledComponent type no longer supports the third generic Theme parameter. Instead add the theme prop to the first Props argument. For example:

    StyledComponent<Props, {}, MyTheme>
    to
    StyledComponent<Props & { theme?: MyTheme }>

Patch Changes

• 22935470 #1588 Thanks @FezVrasta! - StyledComponent Flow type is now polymorphic, that means you can now define the component prop types to get better type safety.
• Updated dependencies [1eaa3a38]:
  • @emotion/serialize@1.0.0-next.0
  • @emotion/core@11.0.0-next.1

@emotion/styled@11.0.0-next.1

Major Changes

• 1eaa3a38 #1600 Thanks @mitchellhamilton! - TypeScript types have been restructured. These changes:

  • Reduce build times when using emotion
  • In many cases remove the need for manually specifying generic parameters for your emotion components.

  If you encounter build issues after upgrade, try removing any manually specified generic types and let them be inferred. Otherwise refer to the breaking changes list below.

  Improvements

  • useTheme added to EmotionTheming interface and can now create your own closed variation of withTheme. More information in the docs under the theming section.
  • Union types as props are better supported and should be inferred properly
  • Build times should be reduced significantly in larger projects.

  Breaking changes

  • withTheme can now have the Theme type specified when calling it. For example withTheme<MyTheme>(MyComponent)

    Breaking change: Generic argument changed, if you were specifying the ComponentType you will need to remove the generic parameter. Recommend following example setup in the TypeScript docs under theming section

  • css function has been restricted to prevent passing of invalid types

  • CreateStyled functions no longer take a second ExtraProps argument. Instead move it to after the create styled call. For example

    styled<typeof MyComponent, ExtraProps>(MyComponent)({})
    to
    styled(MyComponent)<ExtraProps>({})

  • StyledComponent type no longer supports the third generic Theme parameter. Instead add the theme prop to the first Props argument. For example:

    StyledComponent<Props, {}, MyTheme>
    to
    StyledComponent<Props & { theme?: MyTheme }>

Patch Changes

• 22935470 #1588 Thanks @FezVrasta! - StyledComponent Flow type is now polymorphic, that means you can now define the component prop types to get better type safety.
• Updated dependencies [1eaa3a38, 22935470]:
  • @emotion/styled-base@11.0.0-next.1
  • babel-plugin-emotion@11.0.0-next.1
  • @emotion/core@11.0.0-next.1

babel-plugin-emotion@11.0.0-next.1

Patch Changes

• Updated dependencies [1eaa3a38]:
  • @emotion/serialize@1.0.0-next.0

@emotion/core@11.0.0-next.1

Patch Changes

• Updated dependencies [1eaa3a38, 22935470]:
  • @emotion/css@11.0.0-next.1
  • emotion-theming@11.0.0-next.1
  • @emotion/serialize@1.0.0-next.0
  • @emotion/styled@11.0.0-next.1

create-emotion@11.0.0-next.1

Patch Changes

• Updated dependencies [1eaa3a38]:
  • @emotion/serialize@1.0.0-next.0

jest-emotion@11.0.0-next.1

Patch Changes

• e67a5be9 #967 Thanks @Andarist! - Take specificity into account when matching styles

• e67a5be9 #967 Thanks @Andarist! - Match rules in declarations with component used as a selector

• Updated dependencies []:

  • @emotion/core@11.0.0-next.1

@emotion/native@11.0.0-next.1

Patch Changes

• Updated dependencies [1eaa3a38]:
  • emotion-theming@11.0.0-next.1
  • @emotion/primitives-core@11.0.0-next.1

@emotion/primitives-core@11.0.0-next.1

Patch Changes

• Updated dependencies []:
  • @emotion/core@11.0.0-next.1

@emotion/primitives@11.0.0-next.1

Patch Changes

• Updated dependencies [1eaa3a38]:
  • emotion-theming@11.0.0-next.1
  • babel-plugin-emotion@11.0.0-next.1
  • @emotion/primitives-core@11.0.0-next.1