Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
11.9.0
->11.10.4
11.8.1
->11.10.4
Release Notes
emotion-js/emotion
v11.10.4
Compare Source
Patch Changes
#2867
89b6dbb3
Thanks @Andarist! - Externalized code referencingReact.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 referencesuseInsertionEffect
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 referenceuseInsertionEffect
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 touseInsertionEffect
in the process.Note that we don't recommend bundling Emotion. You should have very specific reasons to do so.
Updated dependencies [
89b6dbb3
]:v11.10.0
Compare Source
Minor Changes
#2819
bbad8c79
Thanks @nicksrandall! -exports
field has been added to thepackage.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
bbad8c79
Thanks @nicksrandall! - Thanks to the addedexports
field, the package now includes aworker
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
bbad8c79
,bbad8c79
]:v11.9.3
Compare Source
Patch Changes
#2759 Thanks @srmagura, @Andarist! - Change the argument of the
shouldForwardProp
option ofstyled
fromPropertyKey
tostring
in the TypeScript definitions.#2333
3055efdd
Thanks @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
3055efdd
Thanks @antongolub! -FilteringStyledOptions
andStyledOptions
types no longer require a type argument for theProps
generic.Updated dependencies [
26e4e3e8
,5e81f213
,3055efdd
]: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.
This PR has been generated by Mend Renovate. View repository job log here.