fix(deps): update emotion monorepo to v11.14.0 #254
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.11.4
->11.14.0
11.11.5
->11.14.1
Release Notes
emotion-js/emotion (@emotion/react)
v11.14.0
Compare Source
Minor Changes
fc4d7bd
Thanks @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
8dc1a6d
,e1bf17e
]:v11.13.5
Compare Source
Patch Changes
#3270
77d930d
Thanks @emmatown! - Fix inconsistent hashes using development vs production bundles/exports
conditions when using@emotion/babel-plugin
withsourceMap: true
(the default). This is particularly visible when using Emotion with the Next.js Pages router where thedevelopment
condition is used when bundling code but not when importing external code with Node.js.Updated dependencies [
77d930d
]:v11.13.3
Compare Source
Patch Changes
#3232
0ce3ed0
Thanks @ENvironmentSet! - Distributecss
prop attachment over props that are union typesUpdated dependencies []:
v11.13.0
Compare Source
Minor Changes
#3198
d8ff8a5
Thanks @Andarist! - Migrated away from relying onprocess.env.NODE_ENV
checks 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
a9f6912
Thanks @Andarist! - Addededge-light
andworkerd
conditions topackage.json
manifest to better serve users using Vercel Edge and Cloudflare Workers.Patch Changes
d8ff8a5
,a9f6912
]:v11.12.0
Compare Source
Patch Changes
9ca22c6
,7f8db2d
,ea2c397
]: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.