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.

Sign up for GitHub

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

Jump to bottom

Update dependency styled-components to v6 #39

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

Update dependency styled-components to v6 #39

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 28, 2023 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
styled-components (source) ^5.2.1 -> ^6.0.0 age adoption passing confidence

Release Notes

styled-components/styled-components (styled-components)

v6.1.13

Compare Source

v6.1.12

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.1.11...v6.1.12

v6.1.11

Compare Source

v6.1.10

Compare Source

v6.1.9

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.1.8...v6.1.9

v6.1.8

Compare Source

Revert adding peerDependencies from v6.1.7; apparently some build tools do not respect peerDependenciesMeta[package].optional which is causing issues. Will revisit at a later date if possible.

Full Changelog: styled-components/styled-components@v6.1.7...v6.1.8

v6.1.7

Compare Source

What's Changed

  • chore: add all missing peer dependency statements by @​quantizor in https://github.com/styled-components/styled-components/pull/4243

    NOTE: this change may cause some installed dependency duplication until this NPM bug is addressed but yarn and pnpm have correct behavior. Bun also has a similar bug.

    Overall these changes ensure that styled-components is specifying a known working version of all utilized libraries, while instructing the client package manager that higher semver-compliant versions are permissible and should work, assuming the relevant libraries are compliant in practice.

Full Changelog: styled-components/styled-components@v6.1.6...v6.1.7

v6.1.6

Compare Source

What's Changed

Full Changelog: styled-components/styled-components@v6.1.5...v6.1.6

v6.1.5

Compare Source

What's Changed

Full Changelog: styled-components/styled-components@v6.1.4...v6.1.5

v6.1.4

Compare Source

What's Changed

Full Changelog: styled-components/styled-components@v6.1.3...v6.1.4

v6.1.3

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.1.2...v6.1.3

v6.1.2

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.1.1...v6.1.2

v6.1.1

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.1.0...v6.1.1

v6.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.0.9...v6.1.0

v6.0.9

Compare Source

fix bundling to not hardcode window (should fix some testing use cases that were incorrectly assuming a server environment when JSDOM and similar are in use)

Full Changelog: styled-components/styled-components@v6.0.8...v6.0.9

v6.0.8

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.0.7...v6.0.8

v6.0.7

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.0.6...v6.0.7

v6.0.6

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.0.5...v6.0.6

v6.0.5

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.0.4...v6.0.5

v6.0.4

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.0.3...v6.0.4

v6.0.3

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.0.2...v6.0.3

v6.0.2

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.0.1...v6.0.2

v6.0.1

Compare Source

Fixed an issue where a dev-time warning was being triggered too eagerly.

Full Changelog: styled-components/styled-components@v6.0.0...v6.0.1

v6.0.0

Compare Source

yarn add styled-components

Changed in this version

  • fix(types): prevent prop bleed on styling properties (fixes #​4053, c0f8015)
  • feat(types): ship csstype via "CSS" namespace (e6c4f0a)
  • chore: bump stylis to 4.3 (fixes #​4007, fa58875)
  • reduced some sources of unnecessary branching logic

Breaking changes in v6

Migration guide → https://styled-components.com/docs/faqs#what-do-i-need-to-do-to-migrate-to-v6

  • now using stylis v4 (if using stylis-plugin-rtl you'll need to upgrade to the newer version)
  • styled-components now provides its own types; if you installed @types/styled-components in the past, you'll want to remove it
  • dropped $as and $forwardedAs props (use as or forwardedAs)
  • dropped automatic prop filtering; use transient props ($ prefix) for stuff you don't want to be passed to child component / HTML
  • StyleSheetManager
    • replaced disableVendorPrefixes with enableVendorPrefixes prop
    • dropped automatic vendor prefixing; if you need to support older browsers, you can re-enable it easily with the above prop 
      <StyleSheetManager enableVendorPrefixes>
  {/* your React tree and ThemeProvider goes here */}
</StyleSheetManager>
  • dropped deprecated withComponent API (87f511a); use "as" prop instead
  • node >= 14 needed

Full Changelog: styled-components/styled-components@v5.3.7...v6.0.0

v5.3.11

Compare Source

Removed use of the useDebugValue hook to rectify older React support.

Full Changelog: styled-components/styled-components@v5.3.10...v5.3.11

v5.3.10

Compare Source

What's Changed

Full Changelog: styled-components/styled-components@v5.3.9...v5.3.10

v5.3.9

Compare Source

What's Changed

Full Changelog: styled-components/styled-components@v5.3.8...v5.3.9

v5.3.8

Compare Source

What's Changed

fix(constants): rework process env guard

Full Changelog: styled-components/styled-components@v5.3.7-fixed...v5.3.8

v5.3.7

Compare Source

v5.3.6

Compare Source

What's Changed

Deprecations

  • $as and $forwardedAs will be removed in the next major version, use the unprefixed props instead

New Contributors

Full Changelog: styled-components/styled-components@v5.3.5...v5.3.6

v5.3.5

Add statement of solidarity against the war on Ukraine 🇺🇦

v5.3.3

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v5.3.1...v5.3.3

v5.3.1

Compare Source

v5.3.0

Compare Source

  • Pass elementToBeCreated as a third parameter to shouldForwardProp so that the user-specified function can decide whether to pass through props based on whether the created element will be a tag or another component. (see #​3436)

  • Fix React Native components accepts function as style prop. (see #​3389)

v5.2.3

Compare Source

fix an issue with an unguarded window accessor in a SSR path (see #​3446)

v5.2.2

Compare Source

  • For React Native based components, pass testID down to the native component if specified for an easier time testing. (see #​3365)

  • Enable users of the babel macro to customize the styled-components import with importModuleName (see #​3422)

  • [fix] COMPLEX_SELECTOR_PREFIX.includes wasn't transpiled (see #​3397)

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 is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update 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
Copy link
Contributor Author

renovate bot commented Jun 28, 2023

⚠ 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: @reach/alert@0.1.5
npm WARN Found: react@17.0.1
npm WARN node_modules/react
npm WARN   react@"^17.0.1" from the root project
npm WARN   13 more (@testing-library/react, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0" from @reach/alert@0.1.5
npm WARN node_modules/@reach/alert
npm WARN   @reach/alert@"^0.1.2" from toasted-notes@3.2.0
npm WARN   node_modules/toasted-notes
npm WARN 
npm WARN Conflicting peer dependency: react@16.14.0
npm WARN node_modules/react
npm WARN   peer react@"^16.8.0" from @reach/alert@0.1.5
npm WARN   node_modules/@reach/alert
npm WARN     @reach/alert@"^0.1.2" from toasted-notes@3.2.0
npm WARN     node_modules/toasted-notes
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @reach/alert@0.1.5
npm WARN Found: react-dom@17.0.1
npm WARN node_modules/react-dom
npm WARN   react-dom@"^17.0.1" from the root project
npm WARN   5 more (@testing-library/react, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react-dom@"^16.8.0" from @reach/alert@0.1.5
npm WARN node_modules/@reach/alert
npm WARN   @reach/alert@"^0.1.2" from toasted-notes@3.2.0
npm WARN   node_modules/toasted-notes
npm WARN 
npm WARN Conflicting peer dependency: react-dom@16.14.0
npm WARN node_modules/react-dom
npm WARN   peer react-dom@"^16.8.0" from @reach/alert@0.1.5
npm WARN   node_modules/@reach/alert
npm WARN     @reach/alert@"^0.1.2" from toasted-notes@3.2.0
npm WARN     node_modules/toasted-notes
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @reach/component-component@0.1.3
npm WARN Found: react@17.0.1
npm WARN node_modules/react
npm WARN   react@"^17.0.1" from the root project
npm WARN   13 more (@testing-library/react, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.4.0" from @reach/component-component@0.1.3
npm WARN node_modules/@reach/component-component
npm WARN   @reach/component-component@"^0.1.3" from @reach/alert@0.1.5
npm WARN   node_modules/@reach/alert
npm WARN 
npm WARN Conflicting peer dependency: react@16.14.0
npm WARN node_modules/react
npm WARN   peer react@"^16.4.0" from @reach/component-component@0.1.3
npm WARN   node_modules/@reach/component-component
npm WARN     @reach/component-component@"^0.1.3" from @reach/alert@0.1.5
npm WARN     node_modules/@reach/alert
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @reach/component-component@0.1.3
npm WARN Found: react-dom@17.0.1
npm WARN node_modules/react-dom
npm WARN   react-dom@"^17.0.1" from the root project
npm WARN   5 more (@testing-library/react, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react-dom@"^16.4.0" from @reach/component-component@0.1.3
npm WARN node_modules/@reach/component-component
npm WARN   @reach/component-component@"^0.1.3" from @reach/alert@0.1.5
npm WARN   node_modules/@reach/alert
npm WARN 
npm WARN Conflicting peer dependency: react-dom@16.14.0
npm WARN node_modules/react-dom
npm WARN   peer react-dom@"^16.4.0" from @reach/component-component@0.1.3
npm WARN   node_modules/@reach/component-component
npm WARN     @reach/component-component@"^0.1.3" from @reach/alert@0.1.5
npm WARN     node_modules/@reach/alert
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @reach/visually-hidden@0.1.4
npm WARN Found: react@17.0.1
npm WARN node_modules/react
npm WARN   react@"^17.0.1" from the root project
npm WARN   13 more (@testing-library/react, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0" from @reach/visually-hidden@0.1.4
npm WARN node_modules/@reach/visually-hidden
npm WARN   @reach/visually-hidden@"^0.1.4" from @reach/alert@0.1.5
npm WARN   node_modules/@reach/alert
npm WARN 
npm WARN Conflicting peer dependency: react@16.14.0
npm WARN node_modules/react
npm WARN   peer react@"^16.8.0" from @reach/visually-hidden@0.1.4
npm WARN   node_modules/@reach/visually-hidden
npm WARN     @reach/visually-hidden@"^0.1.4" from @reach/alert@0.1.5
npm WARN     node_modules/@reach/alert
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @reach/visually-hidden@0.1.4
npm WARN Found: react-dom@17.0.1
npm WARN node_modules/react-dom
npm WARN   react-dom@"^17.0.1" from the root project
npm WARN   5 more (@testing-library/react, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react-dom@"^16.8.0" from @reach/visually-hidden@0.1.4
npm WARN node_modules/@reach/visually-hidden
npm WARN   @reach/visually-hidden@"^0.1.4" from @reach/alert@0.1.5
npm WARN   node_modules/@reach/alert
npm WARN 
npm WARN Conflicting peer dependency: react-dom@16.14.0
npm WARN node_modules/react-dom
npm WARN   peer react-dom@"^16.8.0" from @reach/visually-hidden@0.1.4
npm WARN   node_modules/@reach/visually-hidden
npm WARN     @reach/visually-hidden@"^0.1.4" from @reach/alert@0.1.5
npm WARN     node_modules/@reach/alert
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: airbnb-prop-types@2.16.0
npm WARN Found: react@17.0.1
npm WARN node_modules/react
npm WARN   react@"^17.0.1" from the root project
npm WARN   13 more (@testing-library/react, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"^0.14 || ^15.0.0 || ^16.0.0-alpha" from airbnb-prop-types@2.16.0
npm WARN node_modules/airbnb-prop-types
npm WARN   airbnb-prop-types@"^2.16.0" from enzyme-adapter-utils@1.14.0
npm WARN   node_modules/enzyme-adapter-utils
npm WARN 
npm WARN Conflicting peer dependency: react@16.14.0
npm WARN node_modules/react
npm WARN   peer react@"^0.14 || ^15.0.0 || ^16.0.0-alpha" from airbnb-prop-types@2.16.0
npm WARN   node_modules/airbnb-prop-types
npm WARN     airbnb-prop-types@"^2.16.0" from enzyme-adapter-utils@1.14.0
npm WARN     node_modules/enzyme-adapter-utils
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: connected-react-router@6.0.0
npm ERR! Found: react@17.0.1
npm ERR! node_modules/react
npm ERR!   react@"^17.0.1" from the root project
npm ERR!   peer react@"*" from @testing-library/react@11.2.2
npm ERR!   node_modules/@testing-library/react
npm ERR!     @testing-library/react@"^11.1.0" from the root project
npm ERR!   12 more (@wojtekmaj/enzyme-adapter-react-17, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.4.0" from connected-react-router@6.0.0
npm ERR! node_modules/connected-react-router
npm ERR!   connected-react-router@"^6.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: react@16.14.0
npm ERR! node_modules/react
npm ERR!   peer react@"^16.4.0" from connected-react-router@6.0.0
npm ERR!   node_modules/connected-react-router
npm ERR!     connected-react-router@"^6.0.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/worker/59d8d3/a905b9/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/worker/59d8d3/a905b9/cache/others/npm/_logs/2023-06-28T20_56_20_100Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants