zoltantothcom/Design-Patterns-JavaScript

An in-range update of styled-components is breaking the build 🚨

greenkeeper opened this issue · 4 comments

greenkeeper commented

The dependency styled-components was updated from 4.2.1 to 4.3.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

styled-components is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
Release Notes for v4.3.0

  • 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 components being folded inappropriately when an interim HOC is present (see #2586)

  • Fix theme prop for styled native components, also fixes theme in
    defaultProps for them (see #2576)

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

  • Implement defaultProps folding (see #2597)

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

greenkeeper commented

After pinning to 4.2.1 your tests are passing again. Downgrade this dependency 📌.

greenkeeper commented

Your tests are still failing with this version. Compare changes

Release Notes for v4.3.1
  • Revert #2586; breaks rehydration in dev for certain runtimes like next.js

We'll explore reintroducing it in v5 but better safe than sorry.

greenkeeper commented

Your tests are still failing with this version. Compare changes

greenkeeper commented

Your tests are still failing with this version. Compare changes

Release Notes for v4.4.1

  • 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