-
Notifications
You must be signed in to change notification settings - Fork 3
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
chore(deps): update emotion monorepo to v11.13.0 #379
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/emotion-monorepo
base: main
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 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
bf6522d
to
4957067
Compare
4957067
to
bb18fa9
Compare
bb18fa9
to
315176c
Compare
315176c
to
90007ed
Compare
90007ed
to
f48cd70
Compare
f48cd70
to
15bdd78
Compare
15bdd78
to
68cb293
Compare
68cb293
to
17baf37
Compare
17baf37
to
ebed0ff
Compare
ebed0ff
to
4712ed7
Compare
4712ed7
to
ccc32ae
Compare
ccc32ae
to
07a0a23
Compare
07a0a23
to
12fd0ab
Compare
12fd0ab
to
eb05b39
Compare
eb05b39
to
0f003e5
Compare
0f003e5
to
a22fc92
Compare
a22fc92
to
3a150ce
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.13.0
11.3.0
->11.13.0
Release Notes
emotion-js/emotion (@emotion/react)
v11.13.0
Compare Source
v11.12.0
Compare Source
v11.11.4
Compare Source
Patch Changes
5b82631d
Thanks @iegik! - Renamed an internalhasOwnProperty
tohasOwn
. This avoids problems in CommonJS environments when the consumer tries to prevent prototype pollution withObject.freeze(Object.prototype)
.v11.11.3
Compare Source
Patch Changes
#3101
49c20b4f
Thanks @kyvong! - Fix Theme import for newer Typescript module resolution modesUpdated dependencies [
45c440fb
]: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
Patch Changes
eed5e6cf
Thanks @Andarist! - Fixed importing in Node ESMv11.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
]: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
]:v11.10.0
Compare Source
Minor Changes
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.Patch Changes
bbad8c79
]:v11.9.3
Compare Source
Patch Changes
#2766
5b3f4d78
Thanks @Andarist! -ThemeProviderProps["children"]
was marked as a required prop asThemeProvider
should always wrap some subtree.Updated dependencies [
26e4e3e8
,6c2d7a60
,5e81f213
]:v11.9.0
Compare Source
Patch Changes
#2700
d9357621
Thanks @arturmuller! - Fixed a false positive warning forcontent
properties that includedvar()
.Updated dependencies [
d9357621
]:v11.8.2
Compare Source
Patch Changes
ff3cb164
Thanks @Jack-Works! - ChangeGlobal
component to use theStyleSheet
constructor of the currentcache.sheet
. This is useful whencache.sheet
is not the default implementation. Thanks to that the inner sheet constructed byGlobal
can share the behavior with its "main" sheet that is hold by thecache
.v11.8.1
Compare Source
Patch Changes
39ac5b99
Thanks @Andarist! - Fixed a transpilation issue that causeduseInsertionEffect
to 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.0
Compare Source
Minor Changes
2f27156a
Thanks @Andarist! - Refactored code to use the upcomingReact.useInsertionEffect
when 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
242f7d8c
Thanks @Andarist! - Added@emotion/babel-plugin
as a dependency - this is an actual dependency of the@emotion/react/macro
entrypoint and it has to be explicitly declared to fix compatibility with strict package managers.#2615
3d672acd
Thanks @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.1
Compare Source
Patch Changes
#2577
04681a5f
Thanks @Methuselah96! - ExportKeyframes
type to avoid TypeScript insertingimport("@​emotion/serialize").Keyframes
references into declaration files emitted based on a source files exportingkeyframes
result. This avoids issues with strict package managers that don't allow accessing undeclared dependencies.#2590
1554a7e2
Thanks @Andarist! - Upgraded and pinned the version of Stylis - the CSS parser that Emotion uses under the hood.Updated dependencies [
1554a7e2
]:v11.7.0
Compare Source
Patch Changes
57be9e8c
Thanks @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.0
Compare Source
Minor Changes
eb013d25
Thanks @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.0
Compare Source
Patch Changes
#2498
e5beae8e
Thanks @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
eda5e687
Thanks @Jarred-Sumner! - Fix error loading @emotion/react in alternative JS environmentsUpdated dependencies [
e5beae8e
,9ae4a91a
,f2eda829
]: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 was generated by Mend Renovate. View the repository job log.