-
Notifications
You must be signed in to change notification settings - Fork 0
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 (master) (major) #482
base: master
Are you sure you want to change the base?
Conversation
165cdbb
to
3dfee42
Compare
Codecov Report
@@ Coverage Diff @@
## master #482 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 3 3
Lines 63 63
=========================================
Hits 63 63 Continue to review full report at Codecov.
|
0d2ca6c
to
46f1ce1
Compare
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: package-lock.json
|
46f1ce1
to
61e5923
Compare
61e5923
to
905ff9a
Compare
905ff9a
to
4d099c8
Compare
4d099c8
to
2cc0b74
Compare
|
This PR contains the following updates:
10.2.1
->11.12.0
^10.0.27
->^11.0.0
Release Notes
emotion-js/emotion (@emotion/babel-preset-css-prop)
v11.12.0
Compare Source
v11.11.0
Compare Source
Patch Changes
eed5e6cf
Thanks @Andarist! - Fixed importing in Node ESMv11.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.2.0
Compare Source
Patch Changes
c9b57f36
#2157 Thanks @Andarist! - Fixed an issue withstyled
transformer not respectingautoLabel: 'dev-only'
setting.v11.0.0
Compare Source
Major Changes
f9feab1a
#1575 Thanks @mitchellhamilton! - Removed support for@emotion/styled-base
package. It has been moved to@emotion/styled
and is available as@emotion/styled/base
. This simplifies how the regular and base versions relate to each other and eliminates problems with stricter package managers when@emotion/styled-base
was not installed explicitly by a user.79036056
#967 Thanks @mitchellhamilton! - Remove support for deprecatedinnerRef
propa72e6dc
#1501 Thanks @JakeGinnivan! - TypeScript types have been significantly restructured. These changes:css
function has been restricted to prevent passing invalid typesstyled
's generic parameter has been changed, if you were specifying theComponentType
you will need to remove that generic parameterstyled
no longer takes a secondExtraProps
parameter - instead of that move it to after thestyled
call. So instead of writingstyled<typeof MyComponent, ExtraProps>(MyComponent)({})
you should now be writingstyled(MyComponent)<ExtraProps>({})
If you encounter build issues after upgrade, try removing any manually specified generic types and let them be inferred.
c6431074
#1609 Thanks @tomsseisums! - It's now easier to provide a type forTheme
. Instead of creating custom instances (like before) you can augment the builtinTheme
interface like this:105de5c8
#1572 Thanks @Andarist! -[data-emotion]
attribute on SSRed styled has changed. You should never rely on it though.79036056
#967 Thanks @mitchellhamilton! - Use hooks internally for improved bundle size and a better tree in React DevTools9e998e37
#1817 Thanks @Andarist! - The parser we use (Stylis) got upgraded. It fixes some long-standing parsing edge cases while being smaller and faster 🚀It has been completely rewritten and comes with some breaking changes. The most notable ones that might affect Emotion users are:
prefix
option. This was always limited to turning off all of some of the prefixes as all available prefixes were on by default. Theprefix
option is gone and to customize which prefixes are applied you need to fork (copy-paste) the prefixer plugin and adjust it to your needs. While this being somewhat more problematic to setup at first we believe that the vast majority of users were not customizing this anyway. By not including the possibility to customize this through an extra option the final solution is more performant because there is no extra overhead of checking if a particular property should be prefixed or not.stylisPlugins
. If you plan to use customstylisPlugins
and you want to have your styles prefixed automatically you must include prefixer in your customstylisPlugins
. You can importprefixer
from thestylis
module to do that.@import
rules are no longer special-cased. The responsibility to put them first has been moved to the author of the styles. They also can't be nested within other rules now. It's only possible to write them at the top level of global styles.cf56694
#2088 Thanks @Andarist! - UMD filenames have been changed.Minor Changes
4d3b60d0
#1874 Thanks @connor-baer! - Added basic TS type support foras
prop on styled components. It's possible to pass any component to it but it has no effect on other accepted props. This means that it's not 100% type-safe so use it sparingly and with care.ad77ed24
#1624 Thanks @JakeGinnivan! - AddedCreateStyled
overload to handle whenshouldForwardProp
is a custom type guard for intrinsic props.As an example, if you want to override the type of the
color
prop:18c0d5f4
#1668 Thanks @animecyc! - CustomshouldForwardProp
is being preserved now when using.withComponent
. Also, when passing an additionalshouldForwardProp
in.withComponent
's options (like this:SomeComponent.withComponent('span', { shouldForwardProp })
) it's being composed with the potentially existingshouldForwardProp
.5d692a6a
#1956 Thanks @eps1lon! - Upgradedcsstype
dependency to its v3. This is what we use to provide TypeScript typings for object styles. The upgrade should not affect any consuming code but it's worth mentioning if any edge case scenarios arise.Patch Changes
22935470
#1588 Thanks @FezVrasta! -StyledComponent
Flow type is now polymorphic, that means you can now define the component prop types to get better type safety.58dc08a6
#1837 Thanks @arcanis! - Fixed TS compatibility under PnP environments by making@types/react
an optional peer dependency.Updated dependencies [
c672175b
,923ded01
,e3d7db87
,8a896a31
,c5b12d90
,5e803106
,b8476e08
,debaad9a
,0a4a22ff
,5c55fd17
,b0ad4f0c
,9e998e37
,c65c5d88
,5c7ec859
,a085003d
,c7850e61
,b7d21373
,5d692a6a
,c5b12d90
,c6431074
,828111cd
,9e998e37
,69446cb5
]:emotion-js/emotion (@emotion/core)
v11.0.0
Compare Source
Major Changes
b8476e08
#1675 Thanks @mitchellhamilton! - Rename@emotion/core
to@emotion/react
. Please change any imports of@emotion/core
to import@emotion/react
or use the@emotion/pkg-renaming
ESLint rule from@emotion/eslint-plugin
.v10.3.1
Compare Source
Patch Changes
33c01578
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.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.