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

[greenkeeper]

The dependency styled-components was updated from 4.0.3 to 4.1.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.1.0

• 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)

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]

After pinning to 4.0.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper]

• The dependency styled-components was updated from 4.1.0 to 4.1.1.

Your tests are still failing with this version. Compare changes

Release Notes for v4.1.1

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