Skip to content

Latest commit

 

History

History
143 lines (80 loc) · 7.6 KB

CHANGELOG.md

File metadata and controls

143 lines (80 loc) · 7.6 KB
Raw

@emotion/serialize

1.0.0-next.0

Patch Changes

  • e3d7db87 #1732 Thanks @Andarist! - An additional semicolon is now inserted after interpolated arrays to cover cases when it doesn't have a trailing semi itself and thus breaking composition with styles coming after it.

0.11.15-next.4

Patch Changes

0.12.0-next.3

Minor Changes

  • c643107 #1600 Thanks @joltmode! - Reworked Interpolation-related types. Correct types should now be provided to all flavours of emotion.

0.11.15-next.2

Patch Changes

  • 5c55fd17 #1600 Thanks @Andarist! - Fix to what location generated source maps are pointing in case of composed styles.

0.11.15-next.1

Patch Changes

  • 8a896a31 #1600 Thanks @Andarist! - Throw error about invalid content property values instead of just logging error to the console.

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 }>

0.11.16

Patch Changes

  • Updated dependencies [446e756]:
    • @emotion/hash@0.8.0

0.11.15

Patch Changes

  • 4c62ae9 #1698 Thanks @Andarist! - Add LICENSE file
  • Updated dependencies [4c62ae9]:
    • @emotion/hash@0.7.4
    • @emotion/memoize@0.7.4
    • @emotion/unitless@0.7.5
    • @emotion/utils@0.11.3

0.11.14

Patch Changes

  • a55f3d49 #1581 Thanks @Andarist! - Don't cause invalid rule to be serialized when using object style with falsy value

0.11.13

Patch Changes

0.11.12

Patch Changes

  • 57a767ea #1560 Thanks @Andarist! - Fix composition of styles without a final semicolon in a declaration block

0.11.11

  • Updated dependencies [c81c0033]:
    • @emotion/hash@0.7.3
    • @emotion/memoize@0.7.3

0.11.10

Patch Changes

0.11.9

Patch Changes

  • c257d2a3 #1420 Thanks @Andarist! - Fix for opaque keyframes object being used as value for animation & animationName in object styles

0.11.8

Patch Changes

0.11.7

Patch Changes

  • 757bd86d #1378 Thanks @Andarist! - Fixed issue with camelCased custom properties not being handled correctly in object styles