emotion-js/emotion
### [`v11.10.4`](https://togithub.com/emotion-js/emotion/releases/tag/%40emotion/react%4011.10.4)
[Compare Source](https://togithub.com/emotion-js/emotion/compare/@emotion/react@11.10.0...@emotion/react@11.10.4)
##### Patch Changes
- [#2867](https://togithub.com/emotion-js/emotion/pull/2867) [`89b6dbb3`](https://togithub.com/emotion-js/emotion/commit/89b6dbb3c13d49ef1fa3d88888672d810853f05a) Thanks [@Andarist](https://togithub.com/Andarist)! - Externalized code referencing `React.useInsertionEffect` to a separate `@emotion/use-insertion-effect-with-fallbacks` package. This package should be used in your defined externals if you bundle Emotion for whatever reason. It references `useInsertionEffect` in a very specific way that allows us to use it conditionally. However, if the code consuming Emotion is bundled as a library with Emotion in it then some bundlers might change the way in which we reference `useInsertionEffect` and that might create problems for bundlers used to consume the said library code. By externalizing this new package you can still bundle Emotion if you want to without running into this problem as you won't "destroy" the carefully crafted reference to `useInsertionEffect` in the process.
Note that we don't recommend bundling Emotion. You should have very specific reasons to do so.
- Updated dependencies \[[`89b6dbb3`](https://togithub.com/emotion-js/emotion/commit/89b6dbb3c13d49ef1fa3d88888672d810853f05a)]:
- [@emotion/use-insertion-effect-with-fallbacks](https://togithub.com/emotion/use-insertion-effect-with-fallbacks)[@1](https://togithub.com/1).0.0
### [`v11.10.0`](https://togithub.com/emotion-js/emotion/releases/tag/%40emotion/styled%4011.10.0)
[Compare Source](https://togithub.com/emotion-js/emotion/compare/@emotion/react@11.9.3...@emotion/react@11.10.0)
##### Minor Changes
- [#2819](https://togithub.com/emotion-js/emotion/pull/2819) [`bbad8c79`](https://togithub.com/emotion-js/emotion/commit/bbad8c79937f8dfd5d93bf485c1e9ec44124d228) Thanks [@nicksrandall](https://togithub.com/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.
- [#2819](https://togithub.com/emotion-js/emotion/pull/2819) [`bbad8c79`](https://togithub.com/emotion-js/emotion/commit/bbad8c79937f8dfd5d93bf485c1e9ec44124d228) Thanks [@nicksrandall](https://togithub.com/nicksrandall)! - Thanks to the added `exports` field, the package now includes a `worker` condition that can be utilized by properly configured bundlers when targeting worker-like environments. It fixes the issue with browser-specific files being prioritized by some bundlers when targeting workers.
##### Patch Changes
- Updated dependencies \[[`bbad8c79`](https://togithub.com/emotion-js/emotion/commit/bbad8c79937f8dfd5d93bf485c1e9ec44124d228), [`bbad8c79`](https://togithub.com/emotion-js/emotion/commit/bbad8c79937f8dfd5d93bf485c1e9ec44124d228)]:
- [@emotion/babel-plugin](https://togithub.com/emotion/babel-plugin)[@11](https://togithub.com/11).10.0
- [@emotion/is-prop-valid](https://togithub.com/emotion/is-prop-valid)[@1](https://togithub.com/1).2.0
- [@emotion/serialize](https://togithub.com/emotion/serialize)[@1](https://togithub.com/1).1.0
- [@emotion/utils](https://togithub.com/emotion/utils)[@1](https://togithub.com/1).2.0
### [`v11.9.3`](https://togithub.com/emotion-js/emotion/releases/tag/%40emotion/styled%4011.9.3)
[Compare Source](https://togithub.com/emotion-js/emotion/compare/@emotion/react@11.9.0...@emotion/react@11.9.3)
##### Patch Changes
- [#2759](https://togithub.com/emotion-js/emotion/pull/2759) Thanks [@srmagura](https://togithub.com/srmagura), [@Andarist](https://togithub.com/Andarist)! - Change the argument of the `shouldForwardProp` option of `styled` from `PropertyKey` to `string` in the TypeScript definitions.
- [#2333](https://togithub.com/emotion-js/emotion/pull/2333) [`3055efdd`](https://togithub.com/emotion-js/emotion/commit/3055efddf8f9fb14b148fda466dcb4eb9affc525) Thanks [@Andarist](https://togithub.com/Andarist)! - `shouldForwardProp` has been changed from being a bivariant method to a contravariant function - it improves the type-safety for those that type this option.
- [#2333](https://togithub.com/emotion-js/emotion/pull/2333) [`3055efdd`](https://togithub.com/emotion-js/emotion/commit/3055efddf8f9fb14b148fda466dcb4eb9affc525) Thanks [@antongolub](https://togithub.com/antongolub)! - `FilteringStyledOptions` and `StyledOptions` types no longer require a type argument for the `Props` generic.
- Updated dependencies \[[`26e4e3e8`](https://togithub.com/emotion-js/emotion/commit/26e4e3e8b68479f0e3cb8fbec723da47afd6ac98), [`5e81f213`](https://togithub.com/emotion-js/emotion/commit/5e81f213980e9ba2cfa35256476673b68d47fc33), [`3055efdd`](https://togithub.com/emotion-js/emotion/commit/3055efddf8f9fb14b148fda466dcb4eb9affc525)]:
- [@emotion/serialize](https://togithub.com/emotion/serialize)[@1](https://togithub.com/1).0.4
- [@emotion/is-prop-valid](https://togithub.com/emotion/is-prop-valid)[@1](https://togithub.com/1).1.3
### [`v11.9.0`](https://togithub.com/emotion-js/emotion/releases/tag/%40emotion/react%4011.9.0)
[Compare Source](https://togithub.com/emotion-js/emotion/compare/@emotion/react@11.8.2...@emotion/react@11.9.0)
##### Patch Changes
- [#2700](https://togithub.com/emotion-js/emotion/pull/2700) [`d9357621`](https://togithub.com/emotion-js/emotion/commit/d935762131b1474f2474296ee4706f7ecd59b6dd) Thanks [@arturmuller](https://togithub.com/arturmuller)! - Fixed a false positive warning for `content` properties that included `var()`.
- Updated dependencies \[[`d9357621`](https://togithub.com/emotion-js/emotion/commit/d935762131b1474f2474296ee4706f7ecd59b6dd)]:
- [@emotion/serialize](https://togithub.com/emotion/serialize)[@1](https://togithub.com/1).0.3
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
â™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
[ ] If you want to rebase/retry this PR, click this checkbox.
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
^11.8.2
->11.10.4
^11.8.1
->11.10.4
Release Notes
emotion-js/emotion
### [`v11.10.4`](https://togithub.com/emotion-js/emotion/releases/tag/%40emotion/react%4011.10.4) [Compare Source](https://togithub.com/emotion-js/emotion/compare/@emotion/react@11.10.0...@emotion/react@11.10.4) ##### Patch Changes - [#2867](https://togithub.com/emotion-js/emotion/pull/2867) [`89b6dbb3`](https://togithub.com/emotion-js/emotion/commit/89b6dbb3c13d49ef1fa3d88888672d810853f05a) Thanks [@Andarist](https://togithub.com/Andarist)! - Externalized code referencing `React.useInsertionEffect` to a separate `@emotion/use-insertion-effect-with-fallbacks` package. This package should be used in your defined externals if you bundle Emotion for whatever reason. It references `useInsertionEffect` in a very specific way that allows us to use it conditionally. However, if the code consuming Emotion is bundled as a library with Emotion in it then some bundlers might change the way in which we reference `useInsertionEffect` and that might create problems for bundlers used to consume the said library code. By externalizing this new package you can still bundle Emotion if you want to without running into this problem as you won't "destroy" the carefully crafted reference to `useInsertionEffect` in the process. Note that we don't recommend bundling Emotion. You should have very specific reasons to do so. - Updated dependencies \[[`89b6dbb3`](https://togithub.com/emotion-js/emotion/commit/89b6dbb3c13d49ef1fa3d88888672d810853f05a)]: - [@emotion/use-insertion-effect-with-fallbacks](https://togithub.com/emotion/use-insertion-effect-with-fallbacks)[@1](https://togithub.com/1).0.0 ### [`v11.10.0`](https://togithub.com/emotion-js/emotion/releases/tag/%40emotion/styled%4011.10.0) [Compare Source](https://togithub.com/emotion-js/emotion/compare/@emotion/react@11.9.3...@emotion/react@11.10.0) ##### Minor Changes - [#2819](https://togithub.com/emotion-js/emotion/pull/2819) [`bbad8c79`](https://togithub.com/emotion-js/emotion/commit/bbad8c79937f8dfd5d93bf485c1e9ec44124d228) Thanks [@nicksrandall](https://togithub.com/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. - [#2819](https://togithub.com/emotion-js/emotion/pull/2819) [`bbad8c79`](https://togithub.com/emotion-js/emotion/commit/bbad8c79937f8dfd5d93bf485c1e9ec44124d228) Thanks [@nicksrandall](https://togithub.com/nicksrandall)! - Thanks to the added `exports` field, the package now includes a `worker` condition that can be utilized by properly configured bundlers when targeting worker-like environments. It fixes the issue with browser-specific files being prioritized by some bundlers when targeting workers. ##### Patch Changes - Updated dependencies \[[`bbad8c79`](https://togithub.com/emotion-js/emotion/commit/bbad8c79937f8dfd5d93bf485c1e9ec44124d228), [`bbad8c79`](https://togithub.com/emotion-js/emotion/commit/bbad8c79937f8dfd5d93bf485c1e9ec44124d228)]: - [@emotion/babel-plugin](https://togithub.com/emotion/babel-plugin)[@11](https://togithub.com/11).10.0 - [@emotion/is-prop-valid](https://togithub.com/emotion/is-prop-valid)[@1](https://togithub.com/1).2.0 - [@emotion/serialize](https://togithub.com/emotion/serialize)[@1](https://togithub.com/1).1.0 - [@emotion/utils](https://togithub.com/emotion/utils)[@1](https://togithub.com/1).2.0 ### [`v11.9.3`](https://togithub.com/emotion-js/emotion/releases/tag/%40emotion/styled%4011.9.3) [Compare Source](https://togithub.com/emotion-js/emotion/compare/@emotion/react@11.9.0...@emotion/react@11.9.3) ##### Patch Changes - [#2759](https://togithub.com/emotion-js/emotion/pull/2759) Thanks [@srmagura](https://togithub.com/srmagura), [@Andarist](https://togithub.com/Andarist)! - Change the argument of the `shouldForwardProp` option of `styled` from `PropertyKey` to `string` in the TypeScript definitions. - [#2333](https://togithub.com/emotion-js/emotion/pull/2333) [`3055efdd`](https://togithub.com/emotion-js/emotion/commit/3055efddf8f9fb14b148fda466dcb4eb9affc525) Thanks [@Andarist](https://togithub.com/Andarist)! - `shouldForwardProp` has been changed from being a bivariant method to a contravariant function - it improves the type-safety for those that type this option. - [#2333](https://togithub.com/emotion-js/emotion/pull/2333) [`3055efdd`](https://togithub.com/emotion-js/emotion/commit/3055efddf8f9fb14b148fda466dcb4eb9affc525) Thanks [@antongolub](https://togithub.com/antongolub)! - `FilteringStyledOptions` and `StyledOptions` types no longer require a type argument for the `Props` generic. - Updated dependencies \[[`26e4e3e8`](https://togithub.com/emotion-js/emotion/commit/26e4e3e8b68479f0e3cb8fbec723da47afd6ac98), [`5e81f213`](https://togithub.com/emotion-js/emotion/commit/5e81f213980e9ba2cfa35256476673b68d47fc33), [`3055efdd`](https://togithub.com/emotion-js/emotion/commit/3055efddf8f9fb14b148fda466dcb4eb9affc525)]: - [@emotion/serialize](https://togithub.com/emotion/serialize)[@1](https://togithub.com/1).0.4 - [@emotion/is-prop-valid](https://togithub.com/emotion/is-prop-valid)[@1](https://togithub.com/1).1.3 ### [`v11.9.0`](https://togithub.com/emotion-js/emotion/releases/tag/%40emotion/react%4011.9.0) [Compare Source](https://togithub.com/emotion-js/emotion/compare/@emotion/react@11.8.2...@emotion/react@11.9.0) ##### Patch Changes - [#2700](https://togithub.com/emotion-js/emotion/pull/2700) [`d9357621`](https://togithub.com/emotion-js/emotion/commit/d935762131b1474f2474296ee4706f7ecd59b6dd) Thanks [@arturmuller](https://togithub.com/arturmuller)! - Fixed a false positive warning for `content` properties that included `var()`. - Updated dependencies \[[`d9357621`](https://togithub.com/emotion-js/emotion/commit/d935762131b1474f2474296ee4706f7ecd59b6dd)]: - [@emotion/serialize](https://togithub.com/emotion/serialize)[@1](https://togithub.com/1).0.3Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
â™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate. View repository job log here.