Skip to content

Latest commit

 

History

History
343 lines (218 loc) · 24.3 KB

CHANGELOG.md

File metadata and controls

343 lines (218 loc) · 24.3 KB
Raw

@emotion/react

11.0.0-rc.0

Major Changes

Patch Changes

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

11.0.0-next.19

Patch Changes

  • Updated dependencies [42df3f3b, 42df3f3b]:
    • @emotion/sheet@1.0.0-next.5
    • @emotion/cache@11.0.0-next.19

11.0.0-next.17

Patch Changes

  • Updated dependencies [76e3dc4d]:
    • @emotion/serialize@1.0.0-next.5

11.0.0-next.16

Patch Changes

  • 58b2bbca #1981 Thanks @Andarist! - Changed the key of the global flag that helps us identify that @emotion/react has been loaded more than once to include the current major version of @emotion/react.

  • Updated dependencies [a8eb4e75, dfe98028, debaad9a, 39be057b, 39be057b]:

    • @emotion/cache@11.0.0-next.16
    • @emotion/utils@1.0.0-next.1
    • @emotion/sheet@1.0.0-next.4
    • @emotion/serialize@0.11.15-next.4

11.0.0-next.15

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

  • Updated dependencies [dc1a0c5e, 5d692a6a]:
    • @emotion/sheet@1.0.0-next.3
    • @emotion/serialize@1.0.0-next.3
    • @emotion/cache@11.0.0-next.15

11.0.0-next.14

Patch Changes

  • 58dc08a6 #1837 Thanks @arcanis! - Fixed TS compatibility under PnP environments by making @types/react an optional peer dependency.

  • f57a7229 #1941 Thanks @Andarist! - The way in which we provide TypeScript support for css prop has changed. Based on usage of our jsx pragma we are able to add support for css prop only for components that support className prop (as our jsx factory function takes provided css prop, resolves it and pass the generated className to the rendered component). This has been implemented using technique described here. What is important - we no longer extend any global interfaces, so people shouldn't bump anymore into type conflicts for the css prop when using different libraries with the css prop support, such as styled-components.

    However, it's not possible to leverage css prop support being added conditionally based on a type of rendered component when one is not using our jsx pragma. For those cases when people use our pragma implicitly (for example when using our @emotion/babel-preset-css-prop) we have added special file that can be imported once to add support for the css prop globally, for all components. Use it like this:

    import {} from '@emotion/react/types/css-prop'

    In this particular case we are forced to extend the existing React.Attributes interface. Previously we've been extending both React.DOMAttributes<T> and JSX.IntrinsicAttributes. This change is really minor and shouldn't affect any consuming code.

  • Updated dependencies [4d3b60d0, 58dc08a6, 6d32d82b]:

    • @emotion/styled@11.0.0-next.14
    • @emotion/css@11.0.0-next.14
    • @emotion/server@11.0.0-next.14

11.0.0-next.13

Major Changes

  • 9e998e37 #1817 Thanks @Andarist! - The parser we use (Stylis) got upgraded. It fixes some long-standing parsing edge cases while being smaller and faster 🚀

    It has been completely rewritten and comes with some breaking changes. Most notable ones that might affect Emotion users are:

    • plugins written for the former Stylis v3 are not compatible with the new version. To learn more on how to write a plugin for Stylis v4 you can check out its README and the source code of core plugins.
    • vendor-prefixing was previously customizable using prefix option. This was always limited to turning off all of some of the prefixes as all available prefixes were on by default. The prefix option is gone and to customize which prefixes are applied you need to fork (copy-paste) the prefixer plugin and adjust it to your needs. While this being somewhat more problematic to setup at first we believe that the vast majority of users were not customizing this anyway. By not including the possibility to customize this through an extra option the final solution is more performant because there is no extra overhead of checking if a particular property should be prefixed or not.
    • Prefixer is now just a plugin which happens to be put in default stylisPlugins. If you plan to use custom stylisPlugins and you want to have your styles prefixed automatically you must include prefixer in your custom stylisPlugins. You can import prefixer from the stylis module to do that.
    • @import rules are no longer special-cased. The responsibility to put them first has been moved to the author of the styles. They also can't be nested within other rules now. It's only possible to write them at the top level of global styles.

Patch Changes

  • Updated dependencies [91046a8c, 9e998e37, 9e998e37, 9e998e37]:
    • @emotion/sheet@1.0.0-next.2
    • @emotion/cache@11.0.0-next.13
    • @emotion/css@11.0.0-next.13
    • @emotion/styled@11.0.0-next.13
    • @emotion/utils@1.0.0-next.0
    • @emotion/server@11.0.0-next.13
    • @emotion/serialize@0.11.15-next.2

11.0.0-next.12

Major Changes

  • 105de5c8 #1572 Thanks @Andarist! - [data-emotion] attribute on SSRed styled has changed. You should never rely on it though.

Patch Changes

  • 7dea6d7a #1734 Thanks @Andarist! - Fixed styles inserted by <Global/> component not inheriting speedy option from a cache passed to a wrapping <CacheProvider/>.
  • be2eb614 #1806 Thanks @Andarist! - Do not warn about @emotion/react being loaded twice in Jest. For some reason Jest sometimes evaluates modules twice when jest.mock is being called.

  • 75e2f9e1 #1810 Thanks @Andarist! - Add a dev-only warning about styles created with css from @emotion/react being passed to cx from <ClassNames/>.

  • Updated dependencies [e3d7db87, 105de5c8, 105de5c8, 5bea60b1, 105de5c8, 105de5c8]:

    • @emotion/serialize@1.0.0-next.1
    • @emotion/server@11.0.0-next.12
    • @emotion/styled@11.0.0-next.12
    • @emotion/cache@11.0.0-next.12
    • @emotion/css@11.0.0-next.12

11.0.0-next.11

Patch Changes

  • Updated dependencies [f08ef5a3, b79781f8]:
    • @emotion/serialize@0.11.15-next.4
    • @emotion/styled@11.0.0-next.11
    • @emotion/css@11.0.0-next.11

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.

Patch Changes

  • affed3dd #1600 Thanks @Andarist! - Fix issue with published TypeScript test files augmenting Theme interface.

11.0.0-next.7

Patch Changes

  • 5c55fd17 #1600 Thanks @Andarist! - Fix to what location generated source maps are pointing in case of composed styles.
  • Updated dependencies [5c55fd17, 729ef9d8]:
    • @emotion/serialize@0.11.15-next.2
    • @emotion/styled@11.0.0-next.7

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

  • Updated dependencies [923ded01, 4a891bf6, 843bfb11]:
    • @emotion/styled@11.0.0-next.6
    • @emotion/cache@11.0.0-next.6
    • @emotion/sheet@0.10.0-next.0
    • @emotion/css@11.0.0-next.6

11.0.0-next.5

Patch Changes

  • Updated dependencies [ad77ed24, 99c6b7e2]:
    • @emotion/styled@11.0.0-next.5
    • emotion-theming@11.0.0-next.5

11.0.0-next.4

Patch Changes

  • Updated dependencies [e6e079c3]:
    • @emotion/styled@11.0.0-next.4
    • emotion-theming@11.0.0-next.4

11.0.0-next.3

Patch Changes

  • a085003d #1600 Thanks @Andarist! - Add missing #__PURE__ annotations
  • Updated dependencies [8a896a31, a085003d, f9feab1a]:
    • @emotion/serialize@0.11.15-next.1
    • @emotion/styled@11.0.0-next.3
    • @emotion/css@11.0.0-next.3
    • emotion-theming@11.0.0-next.3

11.0.0-next.2

Major Changes

Patch Changes

  • Updated dependencies [79036056, 79036056]:
    • @emotion/styled@11.0.0-next.2
    • emotion-theming@11.0.0-next.2

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

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

  • Updated dependencies [302bdba1]:
    • @emotion/cache@11.0.0-next.0
    • @emotion/css@11.0.0-next.0
    • emotion@11.0.0-next.0
    • emotion-server@11.0.0-next.0
    • emotion-theming@11.0.0-next.0
    • @emotion/styled@11.0.0-next.0

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

  • 4c62ae9 #1698 Thanks @Andarist! - Add LICENSE file
  • Updated dependencies [4c62ae9]:
    • @emotion/cache@10.0.27
    • @emotion/css@10.0.27
    • emotion-server@10.0.27
    • emotion-theming@10.0.27
    • emotion@10.0.27
    • @emotion/serialize@0.11.15
    • @emotion/sheet@0.9.4
    • @emotion/styled@10.0.27
    • @emotion/utils@0.11.3

10.0.22

Patch Changes

  • 2fc75f26 #1548 Thanks @Andarist! - Accept objects as className in jsx-created components (they are stringified) to match React behavior

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