Skip to content

Latest commit

 

History

History
183 lines (102 loc) · 13.5 KB

CHANGELOG.md

File metadata and controls

183 lines (102 loc) · 13.5 KB
Raw

@emotion/babel-preset-css-prop

11.10.0

Minor Changes

  • #2819 bbad8c79 Thanks @nicksrandall! - exports field has been added to the package.json manifest. This fixes how our default exports are treated by Node.js when using their native support for ES modules. It also 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]:
    • @emotion/babel-plugin@11.10.0
    • @emotion/babel-plugin-jsx-pragmatic@0.2.0

11.2.0

Patch Changes

11.0.0

Major Changes

  • 9e3671c4 #2076 Thanks @Andarist! - Removed runtime option that was introduced to this preset and deprecated shortly after that. If you want to configure runtime: "automatic", replace @emotion/babel-preset-css-prop with @babel/preset-react and @emotion/babel-plugin. You can find out how to configure things properly here: https://emotion.sh/docs/css-prop#babel-preset

  • c5b12d90 #1220 Thanks @mitchellhamilton! - Removed support for the instances option, any usage of it should be replaced with the importMap option

  • c7850e61 #1656 Thanks @Andarist! - autoLabel option no longer is a simple boolean. Instead we accept now 3 values: dev-only (the default), always and never.

    Each possible value for this option produces different output code:

    • with dev-only we optimize the production code, so there are no labels added there, but at the same time we keep labels for development environments,
    • with always we always add labels when possible,
    • with never we disable this entirely and no labels are added.

Minor Changes

  • c5b12d90 #1220 Thanks @mitchellhamilton! - Added the importMap option which allows you to tell @emotion/babel-plugin what imports it should look at to determine what it should transform so if you re-export Emotion's exports, you can still use the Babel transforms

  • c672175b #1130 Thanks @jtmthf! - Adjust how arrays passed to css prop are transformed so function elements can be resolved at runtime.

Patch Changes

11.0.0-rc.0

Major Changes

Patch Changes

  • Updated dependencies [9c4ebc16]:
    • @emotion/babel-plugin@11.0.0-rc.0

11.0.0-next.10

Major Changes

  • c7850e61 #1656 Thanks @Andarist! - autoLabel option no longer is a simple boolean. Instead we accept now 3 values: dev-only (the default), always and never.

    Each possible value for this option produces different output code:

    • with dev-only we optimize the production code, so there are no labels added there, but at the same time we keep labels for development environments,
    • with always we always add labels when possible,
    • with never we disable this entirely and no labels are added.

Patch Changes

  • Updated dependencies [b8476e08, c7850e61]:
    • @emotion/babel-plugin@11.0.0-next.10

11.0.0-next.8

Minor Changes

  • c643107 #1609 Thanks @joltmode! - Adjust how arrays passed to css prop are transformed so function elements can be resolved at runtime.

Patch Changes

  • Updated dependencies [c643107]:
    • babel-plugin-emotion@11.0.0-next.8

11.0.0-next.6

Minor Changes

Patch Changes

11.0.0-next.3

Major Changes

Minor Changes

  • c5b12d90 #1220 Thanks @mitchellhamilton! - Added the importMap option which allows you to tell babel-plugin-emotion what imports it should look at to determine what it should transform so if you re-export Emotion's exports, you can still use the Babel transforms

Patch Changes

11.0.0-next.0

Patch Changes

10.2.1

Patch Changes

  • 32c8528a #2084 Thanks @Andarist! - Only use '@babel/plugin-transform-react-jsx-development' based on the development option when runtime is set to "automatic". The classic runtime is not compatible with this plugin.

10.2.0

Minor Changes

  • c55fadb4 #2074 Thanks @Andarist! - runtime option has been deprecated. It still works and will continue to work in Emotion 10 but we have found out that including JSX plugin twice in the Babel configuration leads to hard to debug problems and it's not always obvious that some presets include it. If you want to configure runtime: "automatic" just replace @emotion/babel-preset-css-prop with @babel/preset-react and babel-plugin-emotion. You can find out how to configure things properly here: https://emotion.sh/docs/css-prop#babel-preset

10.1.0

Minor Changes

10.0.27

Patch Changes

  • 4c62ae9 #1698 Thanks @Andarist! - Add LICENSE file
  • Updated dependencies [4c62ae9]:
    • babel-plugin-emotion@10.0.27
    • @emotion/babel-plugin-jsx-pragmatic@0.1.5

10.0.23

Patch Changes

  • 539bc0c2 #1576 Thanks @Andarist! - Insert import to @emotion/core after existing imports to avoid ordering issues with polyfills

  • 3927293d #1569 Thanks @Andarist! - Add dev hint about css object (generated by Babel) being stringified by accident

  • Updated dependencies [539bc0c2, 3927293d, b3a0f148]:

    • @emotion/babel-plugin-jsx-pragmatic@0.1.4
    • babel-plugin-emotion@10.0.23

10.0.22

Patch Changes

  • 1bb3efe3 #1554 Thanks @Andarist! - Prepend appended label string with semicolon to avoid problems with declaration blocks without a final semicolon

  • Updated dependencies [1bb3efe3]:

    • babel-plugin-emotion@10.0.22

10.0.17

Patch Changes

10.0.14

Patch Changes