-
Notifications
You must be signed in to change notification settings - Fork 0
Update dependency @emotion/react to v11.14.0 #152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/emotion
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or 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
b0c8281 to
f9e166c
Compare
f9e166c to
0545d4c
Compare
0545d4c to
e8c579c
Compare
e8c579c to
c4ec7c2
Compare
c4ec7c2 to
7830118
Compare
7830118 to
d120f74
Compare
d120f74 to
99475e6
Compare
99475e6 to
d3ecaad
Compare
d3ecaad to
ddad6e5
Compare
ddad6e5 to
8da909a
Compare
8da909a to
ddafcd5
Compare
ddafcd5 to
f03da84
Compare
f03da84 to
18491e2
Compare
18491e2 to
ae1db32
Compare
ae1db32 to
836d171
Compare
836d171 to
05f7fda
Compare
05f7fda to
21a3af8
Compare
21a3af8 to
44eda81
Compare
44eda81 to
6f167c9
Compare
6f167c9 to
9a9d817
Compare
9a9d817 to
f32a54e
Compare
a222250 to
6532826
Compare
6532826 to
04c3bb5
Compare
04c3bb5 to
e996669
Compare
e996669 to
f4a6c67
Compare
f4a6c67 to
1575df5
Compare
1575df5 to
932ce82
Compare
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.4.1→11.14.0Release Notes
emotion-js/emotion (@emotion/react)
v11.14.0Compare Source
Minor Changes
a19d019Thanks @Andarist! - Source code has been migrated to TypeScript. From now on type declarations will be emitted based on that, instead of being hand-written.Patch Changes
e1bf17e]:v11.13.5Compare Source
Patch Changes
#3270
77d930dThanks @emmatown! - Fix inconsistent hashes using development vs production bundles/exportsconditions when using@emotion/babel-pluginwithsourceMap: true(the default). This is particularly visible when using Emotion with the Next.js Pages router where thedevelopmentcondition is used when bundling code but not when importing external code with Node.js.Updated dependencies [
77d930d]:v11.13.3Compare Source
Patch Changes
#3232
0ce3ed0Thanks @ENvironmentSet! - Distributecssprop attachment over props that are union typesUpdated dependencies []:
v11.13.0Compare Source
Minor Changes
#3198
d8ff8a5Thanks @Andarist! - Migrated away from relying onprocess.env.NODE_ENVchecks to differentiate between production and development builds.Development builds (and other environment-specific builds) can be used by using proper conditions (see here). Most modern bundlers/frameworks already preconfigure those for the user so no action has to be taken.
Default files should continue to work in all environments.
#3215
a9f6912Thanks @Andarist! - Addededge-lightandworkerdconditions topackage.jsonmanifest to better serve users using Vercel Edge and Cloudflare Workers.Patch Changes
d8ff8a5,a9f6912]:v11.12.0Compare Source
Patch Changes
#3206
d1994c4Thanks @DiegoAndai! - Improved compatibility with the upcoming@types/reactfor React 19 where the globalJSXnamespace doesn't exist anymore#3208
56109e7Thanks @Andarist! - Only forward definedrefs to improve compatibility with the upcoming React 19Updated dependencies [
9ca22c6,a1e881b,16d8a8c]: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
Minor Changes
336f3d50Thanks @Andarist! - Added support for cascade@layers by updating the underlying parser (stylis).Patch Changes
#3029
eed5e6cfThanks @Andarist! - Fixed importing in Node ESMUpdated dependencies [
336f3d50,eed5e6cf]:v11.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
#2929
13afe030Thanks @Andarist! - The support for@containerqueries has been added by updating the underlying parser (stylis) .Updated dependencies [
13afe030,c02b1214]: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
#2819
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.#2819
bbad8c79Thanks @nicksrandall! - Thanks to the addedexportsfield, the package now includes aworkercondition 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.3Compare Source
Patch Changes
#2759 Thanks @srmagura, @Andarist! - Change the argument of the
shouldForwardPropoption ofstyledfromPropertyKeytostringin the TypeScript definitions.#2333
3055efddThanks @Andarist! -shouldForwardProphas been changed from being a bivariant method to a contravariant function - it improves the type-safety for those that type this option.#2333
3055efddThanks @antongolub! -FilteringStyledOptionsandStyledOptionstypes no longer require a type argument for thePropsgeneric.Updated dependencies [
26e4e3e8,5e81f213,3055efdd]: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
d2531639,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]:Configuration
📅 Schedule: Branch creation - "after 10:30 before 18:00 every weekday" in timezone Asia/Tokyo, 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 this update again.
This PR was generated by Mend Renovate. View the repository job log.