Skip to content
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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 23, 2022

This PR contains the following updates:

Package Type Update Change OpenSSF
@emotion/babel-preset-css-prop (source) devDependencies major 10.2.1 -> 11.12.0 OpenSSF Scorecard
@emotion/core (source) dependencies major ^10.0.27 -> ^11.0.0 OpenSSF Scorecard

Release Notes

emotion-js/emotion (@​emotion/babel-preset-css-prop)

v11.12.0

Compare Source

v11.11.0

Compare Source

Patch Changes

v11.10.0

Compare Source

Minor Changes
  • #​2819 bbad8c79 Thanks @​nicksrandall! - exports field has been added to the package.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

v11.2.0

Compare Source

Patch Changes

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 deprecated innerRef prop

  • a72e6dc #​1501 Thanks @​JakeGinnivan! - TypeScript types have been significantly restructured. These changes:

    • reduce build times when using Emotion, especially in larger projects
    • it's no longer necessary to manually specify generic parameters for your Emotion components in many cases
    • union types as props are better supported and should be inferred properly
    • the css function has been restricted to prevent passing invalid types
    • styled's generic parameter has been changed, if you were specifying the ComponentType you will need to remove that generic parameter
    • styled no longer takes a second ExtraProps parameter - instead of that move it to after the styled call. So instead of writing styled<typeof MyComponent, ExtraProps>(MyComponent)({}) you should now be writing styled(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 for Theme. Instead of creating custom instances (like before) you can augment the builtin Theme interface like this:

    import '@&#8203;emotion/react'
    
    declare module '@&#8203;emotion/react' {
      export interface Theme {
        primaryColor: string
        secondaryColor: string
      }
    }
  • 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 DevTools

  • 9e998e37 #​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:

    • plugins written for the former Stylis v3 are not compatible with the new version. To learn more on how to write a plugin for Stylis v4 you can check out its README and the source code of core plugins.
    • vendor-prefixing was previously customizable using prefix option. This was always limited to turning off all of some of the prefixes as all available prefixes were on by default. The prefix 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.
    • the prefixer is now just a plugin which happens to be included in the default stylisPlugins. If you plan to use custom stylisPlugins and you want to have your styles prefixed automatically you must include prefixer in your custom stylisPlugins. You can import prefixer from the stylis 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 for as 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! - Added CreateStyled overload to handle when shouldForwardProp is a custom type guard for intrinsic props.

    As an example, if you want to override the type of the color prop:

    export const Box = styled('div', {
      shouldForwardProp: (
        propName
      ): propName is Exclude<keyof JSX.IntrinsicElements['div'], 'color'> =>
        propName !== 'color'
    })<{ color: Array<string> }>(props => ({
      color: props.color[0]
    }))
    ;<Box color={['green']} />
  • 18c0d5f4 #​1668 Thanks @​animecyc! - Custom shouldForwardProp is being preserved now when using .withComponent. Also, when passing an additional shouldForwardProp in .withComponent's options (like this: SomeComponent.withComponent('span', { shouldForwardProp })) it's being composed with the potentially existing shouldForwardProp.

  • 5d692a6a #​1956 Thanks @​eps1lon! - Upgraded csstype 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
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
  • #​2576 33c01578 Thanks @​Methuselah96! - Export Keyframes type to avoid TypeScript inserting import("@&#8203;emotion/serialize").Keyframes references into declaration files emitted based on a source files exporting keyframes 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/master-major-emotion-monorepo branch 4 times, most recently from 165cdbb to 3dfee42 Compare March 30, 2022 05:58
@codecov-commenter
Copy link

codecov-commenter commented Mar 30, 2022

Codecov Report

Merging #482 (0d2ca6c) into master (d3c2574) will not change coverage.
The diff coverage is n/a.

@@            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.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d3c2574...0d2ca6c. Read the comment docs.

@renovate renovate bot force-pushed the renovate/master-major-emotion-monorepo branch 3 times, most recently from 0d2ca6c to 46f1ce1 Compare April 5, 2022 18:01
@renovate
Copy link
Contributor Author

renovate bot commented Apr 5, 2022

⚠ Artifact update problem

Renovate 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:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm WARN cli npm v10.2.3 does not support Node.js v16.20.2. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm WARN cli npm v10.2.3 does not support Node.js v16.20.2. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @emotion/[email protected]
npm WARN Found: @emotion/[email protected]
npm WARN node_modules/@emotion/core
npm WARN   @emotion/core@"^11.0.0" from the root project
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer @emotion/core@"^10.0.27" from @emotion/[email protected]
npm WARN node_modules/@emotion/styled
npm WARN   @emotion/styled@"^10.0.27" from @storybook/[email protected]
npm WARN   node_modules/@storybook/theming
npm WARN 
npm WARN Conflicting peer dependency: @emotion/[email protected]
npm WARN node_modules/@emotion/core
npm WARN   peer @emotion/core@"^10.0.27" from @emotion/[email protected]
npm WARN   node_modules/@emotion/styled
npm WARN     @emotion/styled@"^10.0.27" from @storybook/[email protected]
npm WARN     node_modules/@storybook/theming
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @emotion/[email protected]
npm WARN Found: @emotion/[email protected]
npm WARN node_modules/@emotion/core
npm WARN   @emotion/core@"^11.0.0" from the root project
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer @emotion/core@"^10.0.28" from @emotion/[email protected]
npm WARN node_modules/@emotion/styled-base
npm WARN   @emotion/styled-base@"^10.3.0" from @emotion/[email protected]
npm WARN   node_modules/@emotion/styled
npm WARN 
npm WARN Conflicting peer dependency: @emotion/[email protected]
npm WARN node_modules/@emotion/core
npm WARN   peer @emotion/core@"^10.0.28" from @emotion/[email protected]
npm WARN   node_modules/@emotion/styled-base
npm WARN     @emotion/styled-base@"^10.3.0" from @emotion/[email protected]
npm WARN     node_modules/@emotion/styled
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: [email protected]
npm WARN node_modules/react
npm WARN   react@"^17.0.0" from the root project
npm WARN   42 more (@emotion/styled, @emotion/styled-base, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"^0.14 || ^15.0.0 || ^16.0.0-alpha" from [email protected]
npm WARN node_modules/airbnb-prop-types
npm WARN   airbnb-prop-types@"^2.16.0" from [email protected]
npm WARN   node_modules/enzyme-adapter-utils
npm WARN 
npm WARN Conflicting peer dependency: [email protected]
npm WARN node_modules/react
npm WARN   peer react@"^0.14 || ^15.0.0 || ^16.0.0-alpha" from [email protected]
npm WARN   node_modules/airbnb-prop-types
npm WARN     airbnb-prop-types@"^2.16.0" from [email protected]
npm WARN     node_modules/enzyme-adapter-utils
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: @emotion/[email protected]
npm WARN node_modules/@emotion/core
npm WARN   @emotion/core@"^11.0.0" from the root project
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer @emotion/core@"^10.0.27" from [email protected]
npm WARN node_modules/emotion-theming
npm WARN   emotion-theming@"^10.0.27" from @storybook/[email protected]
npm WARN   node_modules/@storybook/theming
npm WARN   1 more (@storybook/ui)
npm WARN 
npm WARN Conflicting peer dependency: @emotion/[email protected]
npm WARN node_modules/@emotion/core
npm WARN   peer @emotion/core@"^10.0.27" from [email protected]
npm WARN   node_modules/emotion-theming
npm WARN     emotion-theming@"^10.0.27" from @storybook/[email protected]
npm WARN     node_modules/@storybook/theming
npm WARN     1 more (@storybook/ui)
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"^17.0.0" from the root project
npm ERR!   peer react@">=16.3.0" from @emotion/[email protected]
npm ERR!   node_modules/@emotion/styled
npm ERR!     @emotion/styled@"^10.0.27" from @storybook/[email protected]
npm ERR!     node_modules/@storybook/theming
npm ERR!       @storybook/theming@"6.4.19" from @storybook/[email protected]
npm ERR!       node_modules/@storybook/addons
npm ERR!         @storybook/addons@"6.4.19" from @storybook/[email protected]
npm ERR!         node_modules/@storybook/builder-webpack4
npm ERR!         7 more (@storybook/client-api, @storybook/core-client, ...)
npm ERR!       5 more (@storybook/api, @storybook/builder-webpack4, ...)
npm ERR!   41 more (@emotion/styled-base, @material-ui/core, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.0.0-0" from [email protected]
npm ERR! node_modules/enzyme-adapter-react-16
npm ERR!   dev enzyme-adapter-react-16@"1.15.5" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^16.0.0-0" from [email protected]
npm ERR!   node_modules/enzyme-adapter-react-16
npm ERR!     dev enzyme-adapter-react-16@"1.15.5" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/6e865a/b7f1c4/cache/others/npm/_logs/2023-11-13T13_16_22_916Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/6e865a/b7f1c4/cache/others/npm/_logs/2023-11-13T13_16_22_916Z-debug-0.log

@renovate renovate bot changed the title chore(deps): update emotion monorepo (master) (major) chore(deps): update emotion monorepo to v11 (master) (major) May 23, 2022
@renovate renovate bot force-pushed the renovate/master-major-emotion-monorepo branch from 46f1ce1 to 61e5923 Compare September 25, 2022 13:11
@renovate renovate bot force-pushed the renovate/master-major-emotion-monorepo branch from 61e5923 to 905ff9a Compare May 28, 2023 09:01
@renovate renovate bot force-pushed the renovate/master-major-emotion-monorepo branch from 905ff9a to 4d099c8 Compare November 13, 2023 13:16
@renovate renovate bot force-pushed the renovate/master-major-emotion-monorepo branch from 4d099c8 to 2cc0b74 Compare July 19, 2024 07:09
Copy link
Contributor Author

renovate bot commented Jul 19, 2024

⚠️ Artifact update problem

Renovate 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:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @emotion/[email protected]
npm WARN Found: @emotion/[email protected]
npm WARN node_modules/@emotion/core
npm WARN   @emotion/core@"^11.0.0" from the root project
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer @emotion/core@"^10.0.27" from @emotion/[email protected]
npm WARN node_modules/@emotion/styled
npm WARN   @emotion/styled@"^10.0.27" from @storybook/[email protected]
npm WARN   node_modules/@storybook/theming
npm WARN 
npm WARN Conflicting peer dependency: @emotion/[email protected]
npm WARN node_modules/@emotion/core
npm WARN   peer @emotion/core@"^10.0.27" from @emotion/[email protected]
npm WARN   node_modules/@emotion/styled
npm WARN     @emotion/styled@"^10.0.27" from @storybook/[email protected]
npm WARN     node_modules/@storybook/theming
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @emotion/[email protected]
npm WARN Found: @emotion/[email protected]
npm WARN node_modules/@emotion/core
npm WARN   @emotion/core@"^11.0.0" from the root project
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer @emotion/core@"^10.0.28" from @emotion/[email protected]
npm WARN node_modules/@emotion/styled-base
npm WARN   @emotion/styled-base@"^10.3.0" from @emotion/[email protected]
npm WARN   node_modules/@emotion/styled
npm WARN 
npm WARN Conflicting peer dependency: @emotion/[email protected]
npm WARN node_modules/@emotion/core
npm WARN   peer @emotion/core@"^10.0.28" from @emotion/[email protected]
npm WARN   node_modules/@emotion/styled-base
npm WARN     @emotion/styled-base@"^10.3.0" from @emotion/[email protected]
npm WARN     node_modules/@emotion/styled
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: [email protected]
npm WARN node_modules/react
npm WARN   react@"^17.0.0" from the root project
npm WARN   42 more (@emotion/styled, @emotion/styled-base, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"^0.14 || ^15.0.0 || ^16.0.0-alpha" from [email protected]
npm WARN node_modules/airbnb-prop-types
npm WARN   airbnb-prop-types@"^2.16.0" from [email protected]
npm WARN   node_modules/enzyme-adapter-utils
npm WARN 
npm WARN Conflicting peer dependency: [email protected]
npm WARN node_modules/react
npm WARN   peer react@"^0.14 || ^15.0.0 || ^16.0.0-alpha" from [email protected]
npm WARN   node_modules/airbnb-prop-types
npm WARN     airbnb-prop-types@"^2.16.0" from [email protected]
npm WARN     node_modules/enzyme-adapter-utils
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: @emotion/[email protected]
npm WARN node_modules/@emotion/core
npm WARN   @emotion/core@"^11.0.0" from the root project
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer @emotion/core@"^10.0.27" from [email protected]
npm WARN node_modules/emotion-theming
npm WARN   emotion-theming@"^10.0.27" from @storybook/[email protected]
npm WARN   node_modules/@storybook/theming
npm WARN   1 more (@storybook/ui)
npm WARN 
npm WARN Conflicting peer dependency: @emotion/[email protected]
npm WARN node_modules/@emotion/core
npm WARN   peer @emotion/core@"^10.0.27" from [email protected]
npm WARN   node_modules/emotion-theming
npm WARN     emotion-theming@"^10.0.27" from @storybook/[email protected]
npm WARN     node_modules/@storybook/theming
npm WARN     1 more (@storybook/ui)
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"^17.0.0" from the root project
npm ERR!   peer react@">=16.3.0" from @emotion/[email protected]
npm ERR!   node_modules/@emotion/styled
npm ERR!     @emotion/styled@"^10.0.27" from @storybook/[email protected]
npm ERR!     node_modules/@storybook/theming
npm ERR!       @storybook/theming@"6.4.19" from @storybook/[email protected]
npm ERR!       node_modules/@storybook/addons
npm ERR!         @storybook/addons@"6.4.19" from @storybook/[email protected]
npm ERR!         node_modules/@storybook/builder-webpack4
npm ERR!         7 more (@storybook/client-api, @storybook/core-client, ...)
npm ERR!       5 more (@storybook/api, @storybook/builder-webpack4, ...)
npm ERR!   41 more (@emotion/styled-base, @material-ui/core, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.0.0-0" from [email protected]
npm ERR! node_modules/enzyme-adapter-react-16
npm ERR!   dev enzyme-adapter-react-16@"1.15.5" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^16.0.0-0" from [email protected]
npm ERR!   node_modules/enzyme-adapter-react-16
npm ERR!     dev enzyme-adapter-react-16@"1.15.5" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-07-19T07_09_10_576Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant