I linked to our own examples as templates.

Aside: JSFiddle has fatal errors for me on Chrome on macOS, so I couldn't run demos from issues at all.

Now there's a single demo and it's very minimal.

This version of gatsby-plugin-sass includes a newer version of node-sass
which supports Node v10.

Two dependencies, node-sass and fsevents, needed to be upgraded in order
to support Node v10. I used the `yarn why [package]` command to find out
which packages depend on them and used `yarn upgrade [package]` to
upgrade top-level packages which ultimately depend on them to the
highest version allowed by ranges specified package.json. The two
packages were webpack-atoms and babel-cli.

Fixes #335.

Update dependencies which didn't work in Node v10

This way commitlint will run locally so that contributors can fix their
commit messages right away, rather than having to wait for CI.

Avoid an unnecessary reflow in the CSSTransition component if the class
name is falsy.

Husky is tricky because it permanently installs hooks in your repo,
which means that they will run on branches where husky isn't installed
(like v1-stable). Because husky doesn't exist there, those hooks were
causing errors, but the latest husky release modifies those to prevent
failures.

…versions

* feat: remove deprecated lifecycle hooks

* build: only run commitlin on PRs

Lets us squash commits

* build: update deps

# [2.4.0](v2.3.1...v2.4.0) (2018-06-27)

### Features

* remove deprecated lifecycle hooks and polyfill for older react versions ([c1ab1cf](c1ab1cf))

### Performance Improvements

* don't reflow when there's no class to add ([d7b898d](d7b898d))