🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

Minor releases and patches available for several npm packages

The dependency styled-components was updated from 4.2.1 to 4.3.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.

Your Greenkeeper Bot 🌴

When you scroll down on the code block and answer the questions, the app navigates to the next question replacing the code block content but it preserves the previous scroll position. The scroll position should be set to top when changing questions to avoid this behaviour.

The dependency react-syntax-highlighter was updated from 10.3.2 to 10.3.3.

🚨 View failing branch.

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

react-syntax-highlighter 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.

Your Greenkeeper Bot 🌴

The example of factory pattern is misleading. Although the definition says,

Define an interface for creating an object, but let subclasses decide which class to instantiate. Factory Method lets a class defer instantiation to subclasses.

But the example doesn't use any subclasses at all. Whereas, Addy Osmani's example explains it pretty well.

The title on the screenshot doesn't match the current one.

hey, it'd be good to have a quick way to share this project on social media, there's a good amount of space at the bottom 😄

In the Pattern References section would it be preferable to display the ES6 code samples before the ES5 code?

Found myself wanting to read it that way since it's becoming more common to use these language features.

The devDependency webpack was updated from 4.33.0 to 4.34.0.

🚨 View failing branch.

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

webpack 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.

Your Greenkeeper Bot 🌴

There have been updates to the storybook monorepo:

• • The devDependency @storybook/addon-actions was updated from 5.2.1 to 5.2.2.

• The devDependency @storybook/addon-knobs was updated from 5.2.1 to 5.2.2.
• The devDependency @storybook/addon-links was updated from 5.2.1 to 5.2.2.
• The devDependency @storybook/addon-storyshots was updated from 5.2.1 to 5.2.2.
• The devDependency @storybook/addons was updated from 5.2.1 to 5.2.2.
• The devDependency @storybook/react was updated from 5.2.1 to 5.2.2.

🚨 View failing branch.

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

This monorepo update includes releases of one or more dependencies which all belong to the storybook group definition.

storybook 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.

Your Greenkeeper Bot 🌴

The devDependency eslint-plugin-react was updated from 7.14.0 to 7.14.1.

🚨 View failing branch.

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

eslint-plugin-react 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.

Your Greenkeeper Bot 🌴