Update dependency styled-components to v4.4.1

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
styled-components (source)	dependencies	minor	4.0.3 -> 4.4.1

---

Release Notes

styled-components/styled-components

v4.4.1

Compare Source

• Fix styled-components's react-native import for React Native Web, by @​fiberjw (see #​2797)

• Remove dev-time warning if referencing a theme prop without an outer ThemeProvider, the check for it isn't smart enough to handle cases with "or" or ternary fallbacks and creates undesirable noise in various third party integrations

v4.4.0

Compare Source

• Fix to use ownerDocument instead of global document, by @​yamachig (see #​2721)

• Backport fix for SSR classname mismatches in development mode for some environments like next.js (see #​2701)

• Fix attrs not properly taking precedence over props

• Backport fix where classnames are composed in the wrong order if custom class names are passed in (see #​2760)

• Fix add check for style tag detached - sheet in the style tag is null in this case, by @​newying61 (see #​2707)

v4.3.2

Compare Source

• Fix usage of the "css" prop with the styled-components babel macro (relevant to CRA 2.x users), by @​jamesknelson (see #​2633)

v4.3.1

Compare Source

• Revert #​2586; breaks rehydration in dev for certain runtimes like next.js

v4.3.0

Compare Source

• Make it possible to initialize SC_ATTR and SC_DISABLE_SPEEDY via REACT_APP_* .env variables for easier integration with CRA applications (see #​2501)

• Fix theme prop for styled native components, also fixes theme in
  defaultProps for them.

• Add "forwardedAs" prop to allow deeply passing a different "as" prop value to underlying components
  when using styled() as a higher-order component

• Implement defaultProps folding (see #​2597)

v4.2.1

Compare Source

• Remove className usage checker dev utility due to excessive false-positive noise in certain runtime environments like next.js and the related warning suppression prop (see #​2563).

• Attach displayName to forwardRef function as described in React docs (see #​2508).

• Compatibility with react-native-web 0.11 (see #​2453).

• Add stack trace to .attrs warning (see #​2486).

• Fix functions as values for object literals. (see 2489)

• Remove validation in Babel macro, by @​mAAdhaTTah (see #​2427)

v4.2.0

Compare Source

• Reduced GC pressure when using component selector styles. (see #​2424).

• Add svg tag marker to domElements.js (see #​2389)

• Make the GlobalStyleComponent created by createGlobalStyle call the base constructor with props (see #​2321).

• Move to Mono repository structure with lerna @​imbhargav5 (see #​2326)

• Expose StyleSheetContext and StyleSheetConsumer for you fancy babes doing wild stuff

• Filter suppressClassNameWarning to not to pass down to the wrapped components @​taneba (see #​2365)

• Fix an edge case where React would break streaming inside <textarea> elements, which have special child behavior and aren't a suitable place to inject a style tag (see #​2413)

v4.1.3

Compare Source

• Under the hood code cleanup of the Babel macro, by @​lucleray (see #​2286)

v4.1.2

Compare Source

• Fix function-form attrs to receive the full execution context (including theme) (see #​2210)

• Adjust innerRef deprecation warning to not be fired if wrapping a custom component, since that underlying component may not be on forwardRef yet and actually using the prop (see #​2211)

• Expose the ThemeConsumer and ThemeContext exports for the native and primitives entries (see #​2217)

• Remove createGlobalStyle multimount warning; Concurrent and Strict modes intentionally render the same component multiple times, which causes this warning to be triggered always even when usage is correct in the application (see #​2216)

• Folded components are now targettable via component selector as in v3 if you used the old .extend API (see #​2239)

• Don't treat uppercased strings as tag-like components and don't filter out props from them (see #​2225)

v4.1.1

Compare Source

• Put back the try/catch guard around a part of the flattener that sometimes receives undetectable SFCs (fixes an errand hard error in an edge case)

v4.1.0

Compare Source

• Performance optimization for fully static (no function interpolation) styled-components by avoiding using ThemeConsumer since it isn't necessary, by @​mxstbr (see #​2166)

• Allow disabling "speedy" mode via global SC_DISABLE_SPEEDY variable, by @​devrelm (see #​2185)

  To make use of this, you can either set SC_DISABLE_SPEEDY in your app's entry file or use something like webpack.DefinePlugin to do it at build time:

  webpack.DefinePlugin({
    SC_DISABLE_SPEEDY: true,
  });

• Attrs can now be passed a function (see #​2200); thanks @​oliverlaz for providing an early PoC PR for this!

  e.g.:

  styled.div.attrs(props => ({ 'aria-title': props.title }))``;

• Fix the warnTooManyClasses dev helper not being totally dead code eliminated in production (see #​2200)

• Deprecate functions as object keys for object-form attrs (see #​2200)

  e.g.:

  styled.div.attrs({ 'aria-title': props => props.title })``; // bad
  styled.div.attrs(props => ({ 'aria-title': props.title }))``; // good

  Support for this will be removed in styled-components v5. The primary impetus behind this change is to eliminate confusion around basic functions vs styled-components vs React components provided as values in the object-form attrs constructor, each of which has different handling behaviors. The single outer function to receive the props and then return a props object is conceptually simpler.

• The standalone CDN build is now UMD-compliant and can be used with RequireJS, etc.

• Add pixels to unitless numbers when object interpolation is used, by @​Fer0x (see #​2173)

• Trying to interpolate a non-styled component into CSS is now a hard error, rather than a warning (see #​2173)

---

Renovate configuration

📅 Schedule: 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 has been generated by WhiteSource Renovate. View repository job log here.

[codecov]

Codecov Report

Merging #155 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #155   +/-   ##
=======================================
  Coverage   99.88%   99.88%           
=======================================
  Files          53       53           
  Lines         863      863           
  Branches      139      139           
=======================================
  Hits          862      862           
  Misses          1        1

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6eb8e75...e62d63c. Read the comment docs.