Skip to content

Latest commit

Β 

History

History
251 lines (138 loc) Β· 14.8 KB

CHANGELOG.md

File metadata and controls

251 lines (138 loc) Β· 14.8 KB

@emotion/serialize

1.1.1

Patch Changes

  • #2896 c02b1214 Thanks @Andarist! - Fixed an issue that prevented using content: "element(name)". This is a valid special value and doesn't need to be quoted.

1.1.0

Minor Changes

  • #2819 bbad8c79 Thanks @nicksrandall! - exports field has been added to the package.json manifest. It limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.

Patch Changes

  • Updated dependencies [bbad8c79, bbad8c79]:
    • @emotion/hash@0.9.0
    • @emotion/memoize@0.8.0
    • @emotion/unitless@0.8.0
    • @emotion/utils@1.2.0

1.0.4

Patch Changes

  • #2727 26e4e3e8 Thanks @srmagura! - Changed the error message "Component selectors can only be used in conjunction with @emotion/babel-plugin" to reference the new SWC Emotion plugin which will support component selectors soon.
  • #2572 5e81f213 Thanks @otakustay! - Changed the registered parameter to be declared as optional in the TypeScript definition to match the runtime requirement.

1.0.3

Patch Changes

1.0.2

Patch Changes

  • 830dd0e6 #2279 Thanks @lucasweng! - Fixed the issue with incorrectly throwing errors on valid content values containing open-quote.

1.0.1

Patch Changes

1.0.0

Major Changes

  • c6431074 #1609 Thanks @tomsseisums! - Reworked Interpolation-related types. Correct types should now be provided to all flavours of Emotion.

Minor Changes

  • 5d692a6a #1956 Thanks @eps1lon! - Upgraded csstype dependency to its v3. This is what we use to provide TypeScript typings for object styles. The upgrade should not affect any consuming code but it's worth mentioning if any edge case scenarios arise.

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.
  • 8a896a31 #1611 Thanks @Andarist! - Throw error about invalid content property values instead of just logging error to the console.
  • 5c55fd17 #1653 Thanks @Andarist! - Fix to what location generated source maps are pointing in case of composed styles.

1.0.0-rc.0

Major Changes

Patch Changes

  • Updated dependencies [9c4ebc16]:
    • @emotion/utils@1.0.0-rc.0

1.0.0-next.5

Patch Changes

  • 76e3dc4d #2009 Thanks @Andarist! - Re-release latest prerelease version of this package as it has incorrectly been "downgraded" to 0.x version due to a bug in Changesets. This has caused problems because Emotion 10 had a newer 0.x release and thus version targeting Emotion 10 has been fetched on installs as it has been satisfying the specified dependency range.

0.11.15-next.4

Patch Changes

  • Updated dependencies [debaad9a]:
    • @emotion/utils@1.0.0-next.1

1.0.0-next.3

Minor Changes

  • 5d692a6a #1956 Thanks @eps1lon! - Upgraded csstype dependency to its v3. This is what we use to provide TypeScript typings for object styles. The upgrade should not affect any consuming code but it's worth mentioning if any edge case scenarios arise.

0.11.15-next.2

Patch Changes

  • Updated dependencies [9e998e37]:
    • @emotion/utils@1.0.0-next.0

1.0.0-next.1

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 #1609 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 #1653 Thanks @Andarist! - Fix to what location generated source maps are pointing in case of composed styles.

0.11.15-next.1

Patch Changes

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

1.0.0-next.0

Major Changes

  • a72e6dc0 #1501 Thanks @JakeGinnivan! - 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