Update dependency styled-components to v5.3.5

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
styled-components (source)	5.0.1 -> 5.3.5

---

Release Notes

styled-components/styled-components

v5.3.5

Add statement of solidarity against the war on Ukraine 🇺🇦

v5.3.3

What's Changed

• Backport #​3568 (read from textContent rather than innerHTML during rehydrate) to v5 by @​keeganstreet in https://github.com/styled-components/styled-components/pull/3591
• [v5] generate more complete sourcemaps by @​henryqdineen in https://github.com/styled-components/styled-components/pull/3597

New Contributors

• @​henryqdineen made their first contribution in https://github.com/styled-components/styled-components/pull/3597

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

v5.3.1

Compare Source

• Fix forced server-side mode not triggering global styles (See #​3566)

• Fix SSR collisions caused by insufficient hash inputs and reordering of groups on the client, which is a regression in v5.2.0 (See #​3563)

• Fix dynamic creation React warning for React v18, backported to v5 by @​lynndylanhurley (See #​3564)

• Add missing typeof window check when checking for duplicate instances of styled-components (See #​3553)

• Prevent ServerStyleSheet from emitting empty style tags, which would cause issues in IE11 (See #​3555)

• Support css tagged templates inside style objects, by @​roginfarrer and @​dvingo (See #​3469)

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!

• Allow DISABLE_SPEEDY to be set to false to enable speedy mode in non-production environments (see #​3289) thanks @​FastFedora!

• Enable new style rules can be inserted in the middle of existing sheet when rendering on client after rehydrate. GroupIDAllocator is now changed to find nextFreeGroup by checking reverseRegister, instead of setting it to the end of existing groups. (see #​3233) thanks @​mu29!

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" />);

---

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, click this checkbox.

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.