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

fix(deps): Update dependency styled-components to v6 (main) #79

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

fix(deps): Update dependency styled-components to v6 (main) #79

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 3, 2023 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
styled-components (source) ^5.2 -> ^5.2 || ^6.0.0 age adoption passing confidence
styled-components (source) ^5.3.6 -> ^6.1.13 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

Configuration

📅 Schedule: Branch creation - "before 3am on Monday" (UTC), 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 these updates again.

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

This PR has been generated by Mend Renovate using a curated preset maintained by Sanity. View repository job log here

@socket-security
Copy link

socket-security bot commented Jul 3, 2023 •
edited
Loading

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/[email protected] environment Transitive: filesystem +16 3.79 MB probablyup

🚮 Removed packages: npm/[email protected])

View full report↗︎

@renovate renovate bot force-pushed the renovate/main-styled-components-6.x branch 16 times, most recently from 4345a82 to e5b206c Compare July 9, 2023 11:23
@renovate renovate bot force-pushed the renovate/main-styled-components-6.x branch 10 times, most recently from ec29fa4 to 74df16d Compare July 13, 2023 18:14
@renovate renovate bot force-pushed the renovate/main-styled-components-6.x branch 7 times, most recently from 1dc1feb to 3d3b8ed Compare July 25, 2023 10:43
@renovate renovate bot force-pushed the renovate/main-styled-components-6.x branch 2 times, most recently from 5ed2b3e to 6eeee91 Compare August 3, 2023 14:28
@renovate renovate bot changed the title chore(deps): update dependency styled-components to v6 (main) fix(deps): Update dependency styled-components to v6 (main) Aug 4, 2023
@renovate renovate bot force-pushed the renovate/main-styled-components-6.x branch from 6eeee91 to a7a07c3 Compare September 13, 2023 16:39
@renovate renovate bot force-pushed the renovate/main-styled-components-6.x branch 2 times, most recently from 0090b67 to 65f28e3 Compare October 14, 2023 04:46
@renovate renovate bot force-pushed the renovate/main-styled-components-6.x branch from 65f28e3 to 9f5fa46 Compare November 8, 2023 08:03
@renovate renovate bot force-pushed the renovate/main-styled-components-6.x branch 2 times, most recently from 023304a to 47cc87d Compare December 22, 2023 16:35
@renovate renovate bot force-pushed the renovate/main-styled-components-6.x branch 3 times, most recently from 733adb8 to 4da833f Compare December 27, 2023 21:09
@renovate renovate bot force-pushed the renovate/main-styled-components-6.x branch 2 times, most recently from e5ec2a9 to 58a9b3f Compare January 8, 2024 22:16
@hrvstr
Copy link

hrvstr commented Jan 16, 2024

Hi, can we expect an update to sanity-plugin-dashboard-widget-netlify so that it uses a version styled-components that is compatible with the latest sanity studio? It seems like this should be automatic but I still get errors during install:

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/styled-components
npm ERR!   styled-components@"^6.1.8" from the root project
npm ERR!   peer styled-components@"^5.2 || ^6.0.0" from @sanity/[email protected]
npm ERR!   node_modules/@sanity/dashboard
npm ERR!     @sanity/dashboard@"^3.1.6" from the root project
npm ERR!     peer @sanity/dashboard@"^3.0.0" from [email protected]
npm ERR!     node_modules/sanity-plugin-dashboard-widget-netlify
npm ERR!       sanity-plugin-dashboard-widget-netlify@"^2.0.1" from the root project
npm ERR!   9 more (@sanity/portable-text-editor, @sanity/presentation, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer styled-components@"^5.2" from [email protected]
npm ERR! node_modules/sanity-plugin-dashboard-widget-netlify
npm ERR!   sanity-plugin-dashboard-widget-netlify@"^2.0.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/styled-components
npm ERR!   peer styled-components@"^5.2" from [email protected]
npm ERR!   node_modules/sanity-plugin-dashboard-widget-netlify
npm ERR!     sanity-plugin-dashboard-widget-netlify@"^2.0.1" 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.

@richgcook
Copy link

Is it possible to make this happen? Latest Sanity ^3.39.1 needs ^6 of styled-components but "sanity-plugin-dashboard-widget-netlify" uses ^5

@hrvstr
Copy link

hrvstr commented Apr 30, 2024

Is it possible to make this happen? Latest Sanity ^3.39.1 needs ^6 of styled-components but "sanity-plugin-dashboard-widget-netlify" uses ^5

It would be nice to get an update on this but for now, I can recommend switching to this plugin. It has some additional features as well and is compatible with the latest version of Sanity Studio.

@renovate renovate bot force-pushed the renovate/main-styled-components-6.x branch 2 times, most recently from 114c9c4 to 71f350c Compare May 7, 2024 23:27
@renovate renovate bot force-pushed the renovate/main-styled-components-6.x branch from 71f350c to 2d3db0f Compare May 9, 2024 20:35
@renovate renovate bot force-pushed the renovate/main-styled-components-6.x branch from 2d3db0f to 83bf67f Compare July 17, 2024 17:26
@renovate renovate bot force-pushed the renovate/main-styled-components-6.x branch from 83bf67f to bb7ff99 Compare August 30, 2024 03:41
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
🤖 bot 📦 deps ⚠️ major
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@hrvstr @richgcook