@emotion/use-insertion-effect-with-fallbacks@1.2.0

Minor Changes

• #3279 e1bf17e Thanks @Andarist! - Source code has been migrated to TypeScript.

@emotion/styled@11.14.0

Minor Changes

• #3284 a19d019 Thanks @Andarist! - Source code has been migrated to TypeScript. From now on type declarations will be emitted based on that, instead of being hand-written.

Patch Changes

• Updated dependencies [e1bf17e]:
  • @emotion/use-insertion-effect-with-fallbacks@1.2.0

@emotion/react@11.14.0

Minor Changes

• #3281 fc4d7bd Thanks @Andarist! - Source code has been migrated to TypeScript. From now on type declarations will be emitted based on that, instead of being hand-written.

Patch Changes

• Updated dependencies [8dc1a6d, e1bf17e]:
  • @emotion/cache@11.14.0
  • @emotion/use-insertion-effect-with-fallbacks@1.2.0

@emotion/css-prettifier@1.2.0

Minor Changes

• #3278 282b61d Thanks @Andarist! - Source code has been migrated to TypeScript. From now on type declarations will be emitted based on that, instead of being hand-written.

@emotion/cache@11.14.0

Minor Changes

• #3277 8dc1a6d Thanks @Andarist! - Source code has been migrated to TypeScript. From now on type declarations will be emitted based on that, instead of being hand-written.

@emotion/utils@1.4.2

Patch Changes

• #3270 77d930d Thanks @emmatown! - Fix inconsistent hashes using development vs production bundles/exports conditions when using @emotion/babel-plugin with sourceMap: true (the default). This is particularly visible when using Emotion with the Next.js Pages router where the development condition is used when bundling code but not when importing external code with Node.js.

@emotion/styled@11.13.5

Patch Changes

• #3270 77d930d Thanks @emmatown! - Fix inconsistent hashes using development vs production bundles/exports conditions when using @emotion/babel-plugin with sourceMap: true (the default). This is particularly visible when using Emotion with the Next.js Pages router where the development condition is used when bundling code but not when importing external code with Node.js.

• Updated dependencies [77d930d]:

  • @emotion/serialize@1.3.3
  • @emotion/utils@1.4.2
  • @emotion/babel-plugin@11.13.5

@emotion/serialize@1.3.3

Patch Changes

• #3270 77d930d Thanks @emmatown! - Fix inconsistent hashes using development vs production bundles/exports conditions when using @emotion/babel-plugin with sourceMap: true (the default). This is particularly visible when using Emotion with the Next.js Pages router where the development condition is used when bundling code but not when importing external code with Node.js.

• Updated dependencies [77d930d]:

  • @emotion/utils@1.4.2

@emotion/react@11.13.5

Patch Changes

• #3270 77d930d Thanks @emmatown! - Fix inconsistent hashes using development vs production bundles/exports conditions when using @emotion/babel-plugin with sourceMap: true (the default). This is particularly visible when using Emotion with the Next.js Pages router where the development condition is used when bundling code but not when importing external code with Node.js.

• Updated dependencies [77d930d]:

  • @emotion/serialize@1.3.3
  • @emotion/cache@11.13.5
  • @emotion/utils@1.4.2
  • @emotion/babel-plugin@11.13.5

@emotion/css@11.13.5

Patch Changes

• #3270 77d930d Thanks @emmatown! - Fix inconsistent hashes using development vs production bundles/exports conditions when using @emotion/babel-plugin with sourceMap: true (the default). This is particularly visible when using Emotion with the Next.js Pages router where the development condition is used when bundling code but not when importing external code with Node.js.

• Updated dependencies [77d930d]:

  • @emotion/serialize@1.3.3
  • @emotion/cache@11.13.5
  • @emotion/utils@1.4.2
  • @emotion/babel-plugin@11.13.5