housekeeping: Update emotion monorepo #3179
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.0.0->11.13.311.0.0->11.13.0Release Notes
emotion-js/emotion (@emotion/react)
v11.13.3Compare Source
v11.13.0Compare Source
v11.12.0Compare Source
v11.11.4Compare Source
Patch Changes
5b82631dThanks @iegik! - Renamed an internalhasOwnPropertytohasOwn. This avoids problems in CommonJS environments when the consumer tries to prevent prototype pollution withObject.freeze(Object.prototype).v11.11.3Compare Source
Patch Changes
#3101
49c20b4fThanks @kyvong! - Fix Theme import for newer Typescript module resolution modesUpdated dependencies [
45c440fb]:v11.11.1Compare Source
Patch Changes
9357f337Thanks @naari3! - AddedElementTypeto the Emotion'sJSXnamespace. It's defined in the same way as the one in@types/reactand should make it possible to use components that returnstrings,Promises and other types that are valid in React.v11.11.0Compare Source
Patch Changes
eed5e6cfThanks @Andarist! - Fixed importing in Node ESMv11.10.8Compare Source
Patch Changes
#3025
6bd13425Thanks @Andarist! - Fixed a parsing issue with&within nested functions in declaration values by updating the underlying parser (stylis).Updated dependencies [
6bd13425]:v11.10.6Compare Source
Patch Changes
#2985
4e172c2aThanks @emmatown! - Remove peer dependency on@babel/coreUpdated dependencies [
4e172c2a]:v11.10.5Compare Source
Patch Changes
#2905
4c0005f6Thanks @p-m-p! - Do not warn about@emotion/reactbeing loaded twice in Vitest as that might easily happen with mocked modules.#2929
13afe030Thanks @Andarist! - The support for@containerqueries has been added by updating the underlying parser (stylis) .Updated dependencies [
13afe030,c02b1214,d8a13bca]:v11.10.4Compare Source
Patch Changes
#2867
89b6dbb3Thanks @Andarist! - Externalized code referencingReact.useInsertionEffectto a separate@emotion/use-insertion-effect-with-fallbackspackage. This package should be used in your defined externals if you bundle Emotion for whatever reason. It referencesuseInsertionEffectin 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 referenceuseInsertionEffectand 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 touseInsertionEffectin the process.Note that we don't recommend bundling Emotion. You should have very specific reasons to do so.
Updated dependencies [
89b6dbb3]:v11.10.0Compare Source
Minor Changes
bbad8c79Thanks @nicksrandall! -exportsfield has been added to thepackage.jsonmanifest. 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.Patch Changes
bbad8c79]:v11.9.3Compare Source
Patch Changes
#2766
5b3f4d78Thanks @Andarist! -ThemeProviderProps["children"]was marked as a required prop asThemeProvidershould always wrap some subtree.Updated dependencies [
26e4e3e8,6c2d7a60,5e81f213]:v11.9.0Compare Source
Patch Changes
#2700
d9357621Thanks @arturmuller! - Fixed a false positive warning forcontentproperties that includedvar().Updated dependencies [
d9357621]:v11.8.2Compare Source
Patch Changes
ff3cb164Thanks @Jack-Works! - ChangeGlobalcomponent to use theStyleSheetconstructor of the currentcache.sheet. This is useful whencache.sheetis not the default implementation. Thanks to that the inner sheet constructed byGlobalcan share the behavior with its "main" sheet that is hold by thecache.v11.8.1Compare Source
Patch Changes
39ac5b99Thanks @Andarist! - Fixed a transpilation issue that causeduseInsertionEffectto be referenced directly in the specifiers list of the import statement. This has caused build errors in the consuming tools since the import statement can only reference known exports of a module.v11.8.0Compare Source
Minor Changes
2f27156aThanks @Andarist! - Refactored code to use the upcomingReact.useInsertionEffectwhen it's available (this is a new hook that is going to be introduced in React 18). This shouldn't have any effect on existing codebases and the change should be transparent.Patch Changes
#2609
242f7d8cThanks @Andarist! - Added@emotion/babel-pluginas a dependency - this is an actual dependency of the@emotion/react/macroentrypoint and it has to be explicitly declared to fix compatibility with strict package managers.#2615
3d672acdThanks @srmagura! - Fix an edge case where runtime label extraction in class components led to invalid class names in Firefox. This only affected the development build of Emotion.Updated dependencies [
2f27156a]:v11.7.1Compare Source
Patch Changes
#2577
04681a5fThanks @Methuselah96! - ExportKeyframestype to avoid TypeScript insertingimport("@​emotion/serialize").Keyframesreferences into declaration files emitted based on a source files exportingkeyframesresult. This avoids issues with strict package managers that don't allow accessing undeclared dependencies.#2590
1554a7e2Thanks @Andarist! - Upgraded and pinned the version of Stylis - the CSS parser that Emotion uses under the hood.Updated dependencies [
1554a7e2]:v11.7.0Compare Source
Patch Changes
57be9e8cThanks @srmagura! - Changed the implementation of the runtime label extraction in elements using the css prop (that only happens in development) to one that should yield more consistent results across browsers. This fixes some minor issues with React reporting hydration mismatches that wouldn't happen in production.v11.6.0Compare Source
Minor Changes
eb013d25Thanks @eps1lon! - Fixed hydration mismatches ifReact.useId(an upcoming API in React 18) is used within a tree below our components.Patch Changes
9861a18b]:v11.5.0Compare Source
Patch Changes
#2498
e5beae8eThanks @Andarist! - Fixed an edge case issue with incorrect rules being generated. When a context selector (&) was used not at the beginning of a selector (which is not valid SCSS but is allowed by the Stylis parser that we are using) within a group of selectors containing a pseudoclass then it was not replaced correctly with the current context selector.#2500
eda5e687Thanks @Jarred-Sumner! - Fix error loading @emotion/react in alternative JS environmentsUpdated dependencies [
e5beae8e,9ae4a91a,f2eda829]:v11.4.1Compare Source
Patch Changes
#2441
24557d9dThanks @garronej! - Exposed__unsafe_useEmotionCachewhich can be used to access the current Emotion's cache in an easier way than before. Using this might break 0-config SSR and is not recommended to be used unless there you know what you are doing and you are OK with the mentioned downside.#2424
cd25b62dThanks @tills13! - Use theme context when rendering components at all times. This removes a conditional usage of a React hook that could break Rules of Hooks in some scenarios.#2428
a69929d6Thanks @eps1lon! - Added display names to public React contexts in development builds. This helps to recognize them in React Developer Tools.Updated dependencies [
405af5ca]:v11.4.0Compare Source
Patch Changes
#2334
7d9e74f8Thanks @Andarist! - The Global component no longer replaces style elements from server-rendering on first mount and instead reuses the server-side rendered style elementUpdated dependencies [
38f9d44f]:v11.1.5Compare Source
Patch Changes
d0293508#2240 Thanks @wolszczak96! -asprop has been removed from TypeScript declarations for composite components. This prop has not actually been handled by default bystyledfor those components - to makestyledhandle it you need to provide a customshouldForwardPropthat doesn't forward theasprop.Updated dependencies [
f3c2e81d]:v11.1.4Compare Source
Patch Changes
71ca9be3#2181 Thanks @101arrowz! - Fixed some typing issues with React components with custom generic render functions.v11.1.3Compare Source
Patch Changes
704b0092#2180 Thanks @Andarist! - Fixed an issue with global styles containing pseudo selectors in at-rules not being able to be inserted.Updated dependencies [
704b0092]:v11.1.2Compare Source
Patch Changes
3f8bf70e#2132 Thanks @dcastil! -displayNames have been added toGlobalandClassNamescomponents so React Developer Tools should display those better now.1ee34005#2122 Thanks @dcastil! - Improved label extraction from the stack traces to handle components with numbers in their names.e5843530#2140 Thanks @hasparus! - Fixed an issue withcssprop type not being added to all components that accept a stringclassNamecorrectly.Updated dependencies [
5469d003]:v11.1.1Compare Source
Patch Changes
fdd46bdf#2112 Thanks @Andarist! - Fixed the latest tree-shakeability improvements by adding"sideEffects": falseto all internalpackage.jsonfiles as well. This fixeshoist-non-react-staticsnot being dropped correctly despite of the latest improvements.v11.1.0Compare Source
Patch Changes
0e465d1c#2101 Thanks @Andarist! - Improved tree-shakeability of the package. The main benefit is that bundlers should be able now to drophoist-non-react-staticsif you don't actually use ourwithThemeexport.Configuration
📅 Schedule: Branch creation - "every 2 week on monday" (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 was generated by Mend Renovate. View the repository job log.