Update styled-components in / from 2.3.0 to 2.4.0

[dependencies]

Dependencies.io has updated styled-components (a npm dependency in /) from "2.3.0" to "2.4.0".

2.4.0

More stable class names

• babel-plugin-styled-components@1.4.0
• styled-components@2.4.0

These tandem releases introduce a stabler algorithm for determining the unique hash of each component, which should lead to more consistent class names across environments. (both across dev/test/prod and across client/server when using SSR)

Big thanks to probablyup, ref styled-components/styled-components#1381 and styled-components/babel-plugin-styled-components#112

2.3.3

• Fix the attr filtering optimization removed in v2.3.2 which leads to bundle size improvement, thanks to probablyup (see #1377)
• Move last bits of docs from the README to the website, thanks to Carryon, SaraVieira and JamesJefferyUK

2.3.2

Hotfix release, fixes an issue with v2.3.1 where attributes wouldn't be filtered correctly.

2.3.1

Badge

There's now an official styled-components badge, thanks to iRoachie (see #1363)! Throw that on all the projects you have that use styled-components:

[![style: styled-components](https://img.shields.io/badge/style-%F0%9F%92%85%20styled--components-orange.svg?colorB=daa357&colorA=db748e)](https://github.com/styled-components/styled-components)

Changes

Smaller bundle size

probablyup spent some time removing our warning messages in production mode, reducing the library size by about half a kB min+gzip! (see #1365)

Fix unminified UMD bundle

It turns out our unminified UMD build contained some process.env declarations, which broke when used via a <script> tag in your HTML. This is now fixed, thanks to maciej-ka! (see #1355)

Prettier

Our entire repo is now using Prettier, making it easy to stay consistent with our code style, thanks to existentialism! (see #593)

Update contribution and community guidelines

We spent some time updating our contribution and community guidelines to encourage shallow contributions to ensure the longevity of this project and to remove the core team as bottlenecks from development. The TL;DR is this:

If your Pull Request is merged, regardless of content, you're eligible for push access to the organization on GitHub. This is checked for on pull request merges and an invite is sent automatically.

See our contributing.md for more information on Why and How we do this, and expect a blogpost about it in the near future too. Thanks to orta, alloy and ashfurrow for encouraging and helping us to explore this way of managing open source.