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.10.0
->11.11.1
11.10.0
->11.11.0
Release Notes
emotion-js/emotion (@emotion/react)
v11.11.1
Compare Source
Patch Changes
9357f337
Thanks @naari3! - AddedElementType
to the Emotion'sJSX
namespace. It's defined in the same way as the one in@types/react
and should make it possible to use components that returnstring
s,Promise
s and other types that are valid in React.v11.11.0
Compare Source
Minor Changes
336f3d50
Thanks @Andarist! - Added support for cascade@layer
s by updating the underlying parser (stylis).Patch Changes
#3029
eed5e6cf
Thanks @Andarist! - Fixed importing in Node ESMUpdated dependencies [
336f3d50
,eed5e6cf
,336f3d50
]:v11.10.8
Compare Source
Patch Changes
#3025
6bd13425
Thanks @Andarist! - Fixed a parsing issue with&
within nested functions in declaration values by updating the underlying parser (stylis).Updated dependencies [
6bd13425
,6bd13425
]:v11.10.6
Compare Source
Patch Changes
#2985
4e172c2a
Thanks @emmatown! - Remove peer dependency on@babel/core
Updated dependencies [
4e172c2a
]:v11.10.5
Compare Source
Patch Changes
#2905
4c0005f6
Thanks @p-m-p! - Do not warn about@emotion/react
being loaded twice in Vitest as that might easily happen with mocked modules.#2929
13afe030
Thanks @Andarist! - The support for@container
queries has been added by updating the underlying parser (stylis) .Updated dependencies [
13afe030
,c02b1214
,d8a13bca
]: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
]:Configuration
📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" (UTC), 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.