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 #99

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

Update dependency styled-components to v6 #99

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.0.1 -> 6.1.15 age adoption passing confidence

Release Notes

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

v6.1.15

Compare Source

v6.1.14

Compare Source

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

What's Changed

New Contributors

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

v6.1.1

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)

v5.2.1

Compare Source

Tweak server-side build settings to resolve an issue with jest-dom not being able to pick up generated styles (see #​3308) thanks @​Lazyuki

v5.2.0

Compare Source

  • Make sure StyleSheetManager renders all styles in iframe / child windows (see #​3159) thanks @​eramdam!

  • Rework how components self-reference in extension scenarios (see #​3236); should fix a bunch of subtle bugs around patterns like & + &

  • Fix keyframes not receiving a modified stylis instance when using something like stylis-plugin-rtl (see #​3239)

  • Big performance gain for components using style objects (see #​3239)

  • We no longer emit dynamic classNames for empty rulesets, so some className churn may occur in snapshots

  • Preallocate global style placement to ensure cGS is consistently inserted at the top of the stylesheet; note that this is done in runtime order so, if you have multiple cGS that have overlapping styles, ensure they're defined in code in the sequence you would want them injected (see #​3239)

  • Add "engines" to package.json (currently set to Node 10, the oldest supported LTS distribution) (see #​3201) thanks @​MichaelDeBoey!

Finally, special thanks to @​willheslam for testing and some last minute fixes on this release!

v5.1.1

Compare Source

New Functionality
  • Implement shouldForwardProp API for native and primitive platforms, which was previously missing in [v5.1.0] (see #​3093)
    This has been released under a patch bump instead of a minor, since it's only been missing from Native-support.
Bugfixes
  • Added useTheme hook to named exports for react-primitives entrypoint (see #​2982) thanks @​jladuval!
  • Escape every CSS ident character necessary when converting component display names to class names (see #​3102) thanks @​kripod!

v5.1.0

Compare Source

New Functionality

  • Add shouldForwardProp API (almost the same as emotion's, just a slightly different usage pattern); https://github.com/styled-components/styled-components/pull/3006

    Sometimes when composing multiple higher-order components together, it's possible to get into scenarios when multiple layers consume props by the same name. In the past we've introduced various workarounds for popular props like "as" but this power-user API allows for more granular customization of what props are passed down to descendant component children when using the styled() HOC wrapper.

    When combined with other APIs like .attrs() this becomes a very powerful constellation of abilities.

    Here's how you use it:

    const Comp = styled('div').withConfig({
  shouldForwardProp: (prop, defaultValidatorFn) => !['filterThis'].includes(prop),
})`
  color: red;
`;

render(<Comp filterThis="abc" passThru="def" />);

Renders: 


The second argument `defaultValidatorFn` is what we use internally to validate props based on known HTML attributes. It's provided so you can filter exactly what props you don't wish to pass and then fall-back to the default filtering mechanism if desired.

Other methods on the `styled` HOC like `.attrs` can be chained after `withConfig()`, and before opening your template literal:

```jsx
const Comp = styled('div').withConfig({
  shouldForwardProp: (prop, defaultValidatorFn) => !['filterThis'].includes(prop),
}).attrs({ className: 'foo' })`
  color: red;
`;

render(<Comp filterThis="abc" passThru="def" />);

### Renders: <div className="[generated] foo" passThru="def"></div>

Thanks @​stevesims and all that contributed!

  • Add "transient props" API; https://github.com/styled-components/styled-components/pull/3052

    Think of transient props as a lightweight, but complementary API to shouldForwardProp. Because styled-components allows any kind of prop to be used for styling (a trait shared by most CSS-in-JS libraries, but not the third party library ecosystem in general), adding a filter for every possible prop you might use can get cumbersome.

    Transient props are a new pattern to pass props that are explicitly consumed only by styled components and are not meant to be passed down to deeper component layers. Here's how you use them:

    const Comp = styled.div`
  color: ${props => props.$fg || 'black'};
`;

render(<Comp $fg="red">I'm red!</Comp>);

    Note the dollar sign ($) prefix on the prop; this marks it as transient and styled-components knows not to add it to the rendered DOM element or pass it further down the component hierarchy.

Bugfixes

  • Fix slow SSR Rehydration for malformed CSS and increase fault-tolerance (see #​3018)

  • Change isPlainObject (internal method) to support objects created in a different context (see #​3068) thanks @​keeganstreet!

  • Add support for the <video disablePictureInPicture> (see #​3058) thanks @​egdbear!

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 becomes conflicted, 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 renovate bot force-pushed the renovate/styled-components-6.x branch 2 times, most recently from 9f79910 to 8fe416c Compare July 3, 2023 04:51
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch 2 times, most recently from 7421906 to 0baf395 Compare July 13, 2023 06:53
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from 0baf395 to 37e56d8 Compare July 21, 2023 17:22
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch 2 times, most recently from 0805b9f to cffe3a1 Compare August 3, 2023 14:06
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from cffe3a1 to 1cf51c0 Compare September 13, 2023 18:15
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch 2 times, most recently from 51329b5 to 37d7bdd Compare October 14, 2023 03:38
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from 37d7bdd to 83ba659 Compare November 8, 2023 07:17
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch 2 times, most recently from d82fc5b to ec1a676 Compare December 22, 2023 16:05
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch 3 times, most recently from 92af646 to cd55fe9 Compare December 27, 2023 22:05
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch 2 times, most recently from 19d6882 to 2f87a40 Compare January 8, 2024 22:09
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch 2 times, most recently from df36471 to 889f034 Compare May 7, 2024 22:40
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from 889f034 to 2b43b1b Compare May 9, 2024 19:00
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from 2b43b1b to ecc5a11 Compare July 17, 2024 17:29
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from ecc5a11 to 6ea945d Compare August 30, 2024 03:45
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from 6ea945d to 73e437f Compare January 4, 2025 06:59
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from 73e437f to 335f082 Compare February 5, 2025 17:56
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