An in-range update of node-sass is breaking the build 🚨

[greenkeeper]

The devDependency node-sass was updated from 4.9.4 to 4.10.0.

🚨 View failing branch.

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

node-sass is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ ci/circleci: Your tests failed on CircleCI (Details).

---

Release Notes for v4.10.0

Features

• Add Node 11 support (@xzyfer, #2521)

Supported Environments

OS	Architecture	Node
Windows	x86 & x64	0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11
OSX	x64	0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11
Linux*	x86 & x64	0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8**, 9**, 10**^, 11**
Alpine Linux	x64	4, 6, 7, 8, 9, 10, 11
FreeBSD 10+	amd64	4, 6, 8, 9, 10
FreeBSD 10+	i386	4, 6, 8, 9, 10

*Linux support refers to Ubuntu, Debian, and CentOS 5+
** Not available on CentOS 5
^ Only available on x64

Commits

The new version differs by 6 commits ahead by 6, behind by 1.

• c65a1bf 4.10.0
• c73e2fc feat: Add detecton for Node 11 (module 67)
• 0c31dc2 build: Use GCC 4.9 for Travis Node 10 and 11
• f74e9cd Update .travis.yml
• 97849b2 Add Node 11 to TravisCI
• 4aa3982 Add Node 11 to AppVeyor

See the full diff

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.9.4 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.