Closed greenkeeper[bot] closed 5 years ago
dependency
styled-components was updated from 3.4.10
to 4.0.1
.dependency
styled-components was updated from 3.4.10
to 4.0.2
.Update to this version instead π
dependency
styled-components was updated from 3.4.10
to 4.0.3
.Update to this version instead π
Interpolating a styled component into a string now returns the static component selector (emotion cross-compat)
import styled from 'styled-components';
const Comp = styled.div`
color: red;
`;
`${Comp}`; // .sc-hash
Add suppressClassNameWarning
prop to disable warning when wrapping a React component with styled()
and the className
isn't used, by @Fer0x (see #2156)
Expose ThemeContext to enable static contextType support for React 16.6, by @imbhargav5 (see #2152)
Filter out invalid HTML attributes from attrs
, by @Fer0x (see #2133)
Add warning if an attrs
prop is a function that returns an element, by @timswalling (see #2162)
dependency
styled-components was updated from 3.4.10
to 4.1.0
.Update to this version instead π
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)
dependency
styled-components was updated from 3.4.10
to 4.1.1
.Update to this version instead π
dependency
styled-components was updated from 3.4.10
to 4.1.2
.Update to this version instead π
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)
dependency
styled-components was updated from 3.4.10
to 4.1.3
.
The dependency styled-components was updated from
3.4.10
to4.0.0
.This version is not covered by your current version range.
If you donβt accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
Find out more about this release.
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those donβt help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: