renovate[bot]
commented
2 years ago ⚠ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @mui/x-data-grid@5.8.0
npm ERR! Found: react@18.0.0
npm ERR! node_modules/react
npm ERR! react@"18.0.0" from the root project
npm ERR! peer react@"^17.0.0 || ^18.0.0" from @mui/base@5.0.0-alpha.75
npm ERR! node_modules/@mui/base
npm ERR! @mui/base@"5.0.0-alpha.75" from @mui/material@5.6.0
npm ERR! node_modules/@mui/material
npm ERR! @mui/material@"5.6.0" from the root project
npm ERR! 2 more (@mui/icons-material, @mui/x-data-grid)
npm ERR! 15 more (@mui/icons-material, @mui/material, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^17.0.2" from @mui/x-data-grid@5.8.0
npm ERR! node_modules/@mui/x-data-grid
npm ERR! @mui/x-data-grid@"5.8.0" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: react@17.0.2
npm ERR! node_modules/react
npm ERR! peer react@"^17.0.2" from @mui/x-data-grid@5.8.0
npm ERR! node_modules/@mui/x-data-grid
npm ERR! @mui/x-data-grid@"5.8.0" 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-03-31T20_31_19_808Z-debug-0.log
This PR contains the following updates:
11.9.0->11.13.311.8.1->11.13.0Release Notes
emotion-js/emotion (@emotion/react)
### [`v11.13.3`](https://togithub.com/emotion-js/emotion/compare/@emotion/react@11.13.0...3f468846855ed1c6092922a6317a6f5df0ba8dcc) [Compare Source](https://togithub.com/emotion-js/emotion/compare/@emotion/react@11.13.0...@emotion/react@11.13.3) ### [`v11.13.0`](https://togithub.com/emotion-js/emotion/compare/@emotion/jest@11.11.0...70ad1d33892091e9bc478792fa7da662ed63476a) [Compare Source](https://togithub.com/emotion-js/emotion/compare/@emotion/react@11.12.0...@emotion/react@11.13.0) ### [`v11.12.0`](https://togithub.com/emotion-js/emotion/compare/@emotion/babel-preset-css-prop@11.11.0...d57cfcb6daf48fc5458f91b4db2e072fbc2863e4) [Compare Source](https://togithub.com/emotion-js/emotion/compare/@emotion/react@11.11.4...@emotion/react@11.12.0) ### [`v11.11.4`](https://togithub.com/emotion-js/emotion/releases/tag/%40emotion/react%4011.11.4) [Compare Source](https://togithub.com/emotion-js/emotion/compare/@emotion/react@11.11.3...@emotion/react@11.11.4) ##### Patch Changes - [#3159](https://togithub.com/emotion-js/emotion/pull/3159) [`5b82631d`](https://togithub.com/emotion-js/emotion/commit/5b82631d79a58e87e560024d724b849f3921b6e0) Thanks [@iegik](https://togithub.com/iegik)! - Renamed an internal `hasOwnProperty` to `hasOwn`. This avoids problems in CommonJS environments when the consumer tries to prevent prototype pollution with `Object.freeze(Object.prototype)`. ### [`v11.11.3`](https://togithub.com/emotion-js/emotion/releases/tag/%40emotion/react%4011.11.3) [Compare Source](https://togithub.com/emotion-js/emotion/compare/@emotion/react@11.11.1...@emotion/react@11.11.3) ##### Patch Changes - [#3101](https://togithub.com/emotion-js/emotion/pull/3101) [`49c20b4f`](https://togithub.com/emotion-js/emotion/commit/49c20b4faa3b9aec0ca96066c126cbaaabbf2d5c) Thanks [@kyvong](https://togithub.com/kyvong)! - Fix Theme import for newer Typescript module resolution modes - Updated dependencies \[[`45c440fb`](https://togithub.com/emotion-js/emotion/commit/45c440fbc86b90750f275f497d11382f09ec1d2e)]: - [@emotion/serialize](https://togithub.com/emotion/serialize)[@1](https://togithub.com/1).1.3 ### [`v11.11.1`](https://togithub.com/emotion-js/emotion/releases/tag/%40emotion/react%4011.11.1) [Compare Source](https://togithub.com/emotion-js/emotion/compare/@emotion/react@11.11.0...@emotion/react@11.11.1) ##### Patch Changes - [#3048](https://togithub.com/emotion-js/emotion/pull/3048) [`9357f337`](https://togithub.com/emotion-js/emotion/commit/9357f337200ef38f9c6df5d4dd7c20772478ea42) Thanks [@naari3](https://togithub.com/naari3)! - Added `ElementType` to the Emotion's `JSX` namespace. It's defined in the same way as the one in `@types/react` and should make it possible to use components that return `string`s, `Promise`s and other types that are valid in React. ### [`v11.11.0`](https://togithub.com/emotion-js/emotion/releases/tag/%40emotion/eslint-plugin%4011.11.0) [Compare Source](https://togithub.com/emotion-js/emotion/compare/@emotion/react@11.10.8...@emotion/react@11.11.0) ##### Patch Changes - [#3029](https://togithub.com/emotion-js/emotion/pull/3029) [`eed5e6cf`](https://togithub.com/emotion-js/emotion/commit/eed5e6cf00f94f3011b93825ccce43cb2270c247) Thanks [@Andarist](https://togithub.com/Andarist)! - Fixed importing in Node ESM ### [`v11.10.8`](https://togithub.com/emotion-js/emotion/releases/tag/%40emotion/styled%4011.10.8) [Compare Source](https://togithub.com/emotion-js/emotion/compare/@emotion/react@11.10.6...@emotion/react@11.10.8) ##### Patch Changes - [#3025](https://togithub.com/emotion-js/emotion/pull/3025) [`6bd13425`](https://togithub.com/emotion-js/emotion/commit/6bd13425a2b413150c81e63fad1105d7968b5e6f) Thanks [@Andarist](https://togithub.com/Andarist)! - Fixed a parsing issue with `&` within nested functions in declaration values by updating the underlying parser ([stylis](https://togithub.com/thysultan/stylis)). - Updated dependencies \[[`6bd13425`](https://togithub.com/emotion-js/emotion/commit/6bd13425a2b413150c81e63fad1105d7968b5e6f)]: - [@emotion/babel-plugin](https://togithub.com/emotion/babel-plugin)[@11](https://togithub.com/11).10.8 ### [`v11.10.6`](https://togithub.com/emotion-js/emotion/releases/tag/%40emotion/react%4011.10.6) [Compare Source](https://togithub.com/emotion-js/emotion/compare/@emotion/react@11.10.5...@emotion/react@11.10.6) ##### Patch Changes - [#2985](https://togithub.com/emotion-js/emotion/pull/2985) [`4e172c2a`](https://togithub.com/emotion-js/emotion/commit/4e172c2ae4e5237500ec84688d76ebf253ab1fdc) Thanks [@emmatown](https://togithub.com/emmatown)! - Remove peer dependency on `@babel/core` - Updated dependencies \[[`4e172c2a`](https://togithub.com/emotion-js/emotion/commit/4e172c2ae4e5237500ec84688d76ebf253ab1fdc)]: - [@emotion/babel-plugin](https://togithub.com/emotion/babel-plugin)[@11](https://togithub.com/11).10.6 ### [`v11.10.5`](https://togithub.com/emotion-js/emotion/releases/tag/%40emotion/react%4011.10.5) [Compare Source](https://togithub.com/emotion-js/emotion/compare/@emotion/react@11.10.4...@emotion/react@11.10.5) ##### Patch Changes - [#2905](https://togithub.com/emotion-js/emotion/pull/2905) [`4c0005f6`](https://togithub.com/emotion-js/emotion/commit/4c0005f677d5847e7f931a1473ac58b834606c57) Thanks [@p-m-p](https://togithub.com/p-m-p)! - Do not warn about `@emotion/react` being loaded twice in Vitest as that might easily happen with mocked modules. - [#2929](https://togithub.com/emotion-js/emotion/pull/2929) [`13afe030`](https://togithub.com/emotion-js/emotion/commit/13afe0303e2e54b5869c326e6d9c9dc36a332c02) Thanks [@Andarist](https://togithub.com/Andarist)! - The support for `@container` queries has been added by updating the underlying parser ([stylis](https://togithub.com/thysultan/stylis)) . - Updated dependencies \[[`13afe030`](https://togithub.com/emotion-js/emotion/commit/13afe0303e2e54b5869c326e6d9c9dc36a332c02), [`c02b1214`](https://togithub.com/emotion-js/emotion/commit/c02b12145a94df011e0fd6ffd54197a4d9369783), [`d8a13bca`](https://togithub.com/emotion-js/emotion/commit/d8a13bcae81812d3dff643bcf446709f965f0909)]: - [@emotion/babel-plugin](https://togithub.com/emotion/babel-plugin)[@11](https://togithub.com/11).10.5 - [@emotion/serialize](https://togithub.com/emotion/serialize)[@1](https://togithub.com/1).1.1 - [@emotion/cache](https://togithub.com/emotion/cache)[@11](https://togithub.com/11).10.5 ### [`v11.10.4`](https://togithub.com/emotion-js/emotion/releases/tag/%40emotion/styled%4011.10.4) [Compare Source](https://togithub.com/emotion-js/emotion/compare/@emotion/react@11.10.0...@emotion/react@11.10.4) ##### Patch Changes - [#2867](https://togithub.com/emotion-js/emotion/pull/2867) [`89b6dbb3`](https://togithub.com/emotion-js/emotion/commit/89b6dbb3c13d49ef1fa3d88888672d810853f05a) Thanks [@Andarist](https://togithub.com/Andarist)! - Externalized code referencing `React.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 references `useInsertionEffect` 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 reference `useInsertionEffect` 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 to `useInsertionEffect` in the process. Note that we don't recommend bundling Emotion. You should have very specific reasons to do so. - Updated dependencies \[[`89b6dbb3`](https://togithub.com/emotion-js/emotion/commit/89b6dbb3c13d49ef1fa3d88888672d810853f05a)]: - [@emotion/use-insertion-effect-with-fallbacks](https://togithub.com/emotion/use-insertion-effect-with-fallbacks)[@1](https://togithub.com/1).0.0 ### [`v11.10.0`](https://togithub.com/emotion-js/emotion/releases/tag/%40emotion/babel-plugin%4011.10.0) [Compare Source](https://togithub.com/emotion-js/emotion/compare/@emotion/react@11.9.3...@emotion/react@11.10.0) ##### Minor Changes - [#2819](https://togithub.com/emotion-js/emotion/pull/2819) [`bbad8c79`](https://togithub.com/emotion-js/emotion/commit/bbad8c79937f8dfd5d93bf485c1e9ec44124d228) Thanks [@nicksrandall](https://togithub.com/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 - Updated dependencies \[[`bbad8c79`](https://togithub.com/emotion-js/emotion/commit/bbad8c79937f8dfd5d93bf485c1e9ec44124d228)]: - [@emotion/hash](https://togithub.com/emotion/hash)[@0](https://togithub.com/0).9.0 - [@emotion/memoize](https://togithub.com/emotion/memoize)[@0](https://togithub.com/0).8.0 - [@emotion/serialize](https://togithub.com/emotion/serialize)[@1](https://togithub.com/1).1.0 ### [`v11.9.3`](https://togithub.com/emotion-js/emotion/releases/tag/%40emotion/react%4011.9.3) [Compare Source](https://togithub.com/emotion-js/emotion/compare/@emotion/react@11.9.0...@emotion/react@11.9.3) ##### Patch Changes - [#2766](https://togithub.com/emotion-js/emotion/pull/2766) [`5b3f4d78`](https://togithub.com/emotion-js/emotion/commit/5b3f4d78d54552f9785836bc2cc56d3f789afc47) Thanks [@Andarist](https://togithub.com/Andarist)! - `ThemeProviderProps["children"]` was marked as a required prop as `ThemeProvider` should always wrap some subtree. - Updated dependencies \[[`26e4e3e8`](https://togithub.com/emotion-js/emotion/commit/26e4e3e8b68479f0e3cb8fbec723da47afd6ac98), [`6c2d7a60`](https://togithub.com/emotion-js/emotion/commit/6c2d7a6010af85502ae33d14dcbd3bb62ed7612e), [`5e81f213`](https://togithub.com/emotion-js/emotion/commit/5e81f213980e9ba2cfa35256476673b68d47fc33)]: - [@emotion/serialize](https://togithub.com/emotion/serialize)[@1](https://togithub.com/1).0.4 - [@emotion/cache](https://togithub.com/emotion/cache)[@11](https://togithub.com/11).9.3Configuration
📅 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 is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.