emotion

#2985 4e172c2a Thanks @emmatown! - Remove peer dependency on @babel/core

Updated dependencies [4e172c2a]:

• @emotion/[email protected]

#2985 4e172c2a Thanks @emmatown! - Remove peer dependency on @babel/core

Updated dependencies [4e172c2a]:

• @emotion/[email protected]

#2985 4e172c2a Thanks @emmatown! - Remove peer dependency on @babel/core

Updated dependencies [4e172c2a]:

• @emotion/[email protected]

#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]:

• @emotion/[email protected]
• @emotion/[email protected]
• @emotion/[email protected]

#2929 13afe030 Thanks @Andarist! - The support for @container queries has been added by updating the underlying parser (stylis) .

Updated dependencies [13afe030, c02b1214]:

• @emotion/[email protected]
• @emotion/[email protected]

#2929 13afe030 Thanks @Andarist! - The support for @container queries has been added by updating the underlying parser (stylis) .

Updated dependencies [13afe030, 61c66963, c02b1214, d8a13bca]:

• @emotion/[email protected]
• @emotion/[email protected]
• @emotion/[email protected]
• @emotion/[email protected]

#2890 d8a13bca Thanks @Andarist! - An edge case issue with some specific CSS variables being treated as prefixable declarations got fixed by updating the underlying parser (stylis).

Updated dependencies [61c66963]:

• @emotion/[email protected]

#2929 13afe030 Thanks @Andarist! - Updated the underlying parser (stylis).

Updated dependencies [c02b1214]:

• @emotion/[email protected]

#2884 da1e68e8 Thanks @billyjanitsch! - Fix a dependency conflict when @emotion/jest was installed alongside @types/jest@^29.

#2929 13afe030 Thanks @Andarist! - Updated the underlying parser (stylis).

Updated dependencies [13afe030]:

• @emotion/[email protected]

#2867 89b6dbb3 Thanks @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]:

• @emotion/[email protected]

#2867 89b6dbb3 Thanks @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]:

• @emotion/[email protected]