GithubHelp home page GithubHelp logo

react's Introduction

React

Greenkeeper badge License: MIT

Original MOTTO: An easy way to learn React through examples.

Updated MOTTO: Learning React topic by topic.

Before starting


2/21/19 UPDATE: Many things happened in React and its ecosystem. I will try to update the sections to React 16.8.\* (Hooks and some interesting new APIs) and go deeper in the “Life cycle” paragraph for class-based Components. Also, I will be splitting sections in sub-sections for better understanding and proper grouping.


After several years of contributing, mentoring and working with JS and React, I decided to “put together” some notes linked to recurrent doubts and obstacles that friends and co-workers have to face daily.

This is a pure practical guide (ps, it was at the beginning): please, keep the practical intention present during the course of these "shared notes"; I don´t have the intent of challenging the great and plentiful coaching classes; neither the books/"white papers" that today, you can easily find anywhere (starting with the own Facebook´s proprietary documentation).

My aim, as I stated before (even with the latests addons and updates), is -still- clearly pragmatic. You will see some concepts and technicalities (as general and well-needed context) but you should (perhaps must) complement this "joint exercise" with other materials (I try to avoid quoting or referencing given that, an important part of your training is discovering good sources and picking those that satisfy your own and extremely personal "way to learn". However, taking a look the the mother source will not hurt you: react).

Getting Started

Pre-requisites

You DO need to have an intermediate knowledge of JavaScript and, preferably, some exposure to es2015 or ES6. Even when "more complex topics" (not ordinary ones) are addressed as needed as part of the "lessons" (for example leaks, currying) not having an underlying JS base at all will generate more doubts and it could guide you to frustration, and ultimately, a premature failure. If you don´t have experience with JavaScript, some familiarity with Functional Programming and Prototypes... Please, first resolve the context of this and then come back (btw, if this made you smile, you should be good).

Before proceeding with the tutorial, be sure that you have installed or, install...

Required

  • Node.js
  • Package manager (npm which comes with Node or yarn)

Note: packages, dependencies, libraries... are going to be referenced on-demand. Those whose scope is bigger will be addressed in 09_packages

Recommended

Alternatives

react's People

Contributors

aldiazbw avatar alpersonalwebsite avatar bunchito avatar greenkeeper[bot] avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar

react's Issues

An in-range update of react-router-dom is breaking the build 🚨

The dependency react-router-dom was updated from 5.0.1 to 5.1.0.

🚨 View failing branch.

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

react-router-dom 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.

Status Details
  • WhiteSource Security Check: Oops! An error occurred while running the Security Check.

Please contact the WhiteSource Support team at [email protected] and mention the following scan token: b61c20929160442aba42fb76a5933eae

Release Notes for v5.1.0

Changes

Features

  • Added useParams, useLocation, useHistory, and useRouteMatch hooks (d6224d6)
  • Added support for forwardRef in <Link> (b5528ed)

Bugfixes

  • Don't render <Route children> elements when the <Route> does not match (9665659)
Commits

The new version differs by 49 commits.

  • 0c058ad v5.1.0
  • ce2fdc7 Update size snapshots
  • 01ac3d7 Update build step to use yarn instead of npm
  • 8f49b02 Remove docs on context.router
  • 51325d8 Update export style
  • 3debcd4 Add hooks to documentation website
  • 0721144 Update React to 16.8
  • 0f29d23 Update import/export style
  • 443126b Remove react-router-dom shim from website
  • c4a89e1 Use react-app ESLint config and fix a few issues
  • 6372049 Add some docs about hooks
  • 9c784be Rename useMatch => useRouteMatch
  • a5dd83f Fixed up testing doc from #6903
  • d6224d6 Add some hooks for React 16.8 users
  • 19835fb remove clever example in testing guide (#6903)

There are 49 commits in total.

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 🌴

An in-range update of enzyme is breaking the build 🚨

There have been updates to the enzyme monorepo:

    • The devDependency enzyme was updated from 3.8.0 to 3.9.0.

🚨 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 enzyme group definition.

enzyme 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
  • WhiteSource Security Check: The Security Check found 2 vulnerabilities.

Severity CVSS Score CVE GitHub Issue
Medium 5.0 WS-2019-0019 #4
Medium 5.0 [WS-2019-0032]( "Go to CVE Details") #15

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 🌴

WS-2019-0032 Medium Severity Vulnerability detected by WhiteSource

WS-2019-0032 - Medium Severity Vulnerability

Vulnerable Libraries - js-yaml-3.12.0.tgz, js-yaml-3.12.2.tgz

js-yaml-3.12.0.tgz

YAML 1.2 parser and serializer

path: null

Library home page: https://registry.npmjs.org/js-yaml/-/js-yaml-3.12.0.tgz

Dependency Hierarchy:

  • styled-10.0.5.tgz (Root Library)
    • babel-plugin-emotion-10.0.5.tgz
      • babel-plugin-macros-2.4.3.tgz
        • cosmiconfig-5.0.7.tgz
          • js-yaml-3.12.0.tgz (Vulnerable Library)
js-yaml-3.12.2.tgz

YAML 1.2 parser and serializer

path: /tmp/git/react/basic-react-example[map-with-key]/node_modules/js-yaml/package.json

Library home page: https://registry.npmjs.org/js-yaml/-/js-yaml-3.12.2.tgz

Dependency Hierarchy:

  • react-scripts-2.1.8.tgz (Root Library)
    • eslint-5.12.0.tgz
      • js-yaml-3.12.2.tgz (Vulnerable Library)

Found in HEAD commit: 439c681c5c20d7406c8b96f2e84405bd304e0581

Vulnerability Details

Versions js-yaml prior to 3.13.0 are vulnerable to Denial of Service. By parsing a carefully-crafted YAML file, the node process stalls and may exhaust system resources leading to a Denial of Service.

Publish Date: 2019-03-26

URL: WS-2019-0032

CVSS 2 Score Details (5.0)

Base Score Metrics not available

Suggested Fix

Type: Upgrade version

Origin: https://www.npmjs.com/advisories/788/versions

Release Date: 2019-03-26

Fix Resolution: 3.13.0


Step up your Open Source Security Game with WhiteSource here

An in-range update of react-router-dom is breaking the build 🚨

The dependency react-router-dom was updated from 4.3.1 to 4.4.0.

🚨 View failing branch.

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

react-router-dom 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.

Status Details
  • WhiteSource Security Check: The Security Check found 1 vulnerabilities.

Severity CVSS Score CVE GitHub Issue
Medium 5.0 WS-2019-0019 #4

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 🌴

An in-range update of react is breaking the build 🚨

There have been updates to the react monorepo:

    • The dependency react was updated from 16.8.4 to 16.8.5.

🚨 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 react group definition.

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

Status Details
  • WhiteSource Security Check: The Security Check found 1 vulnerabilities.

Severity CVSS Score CVE GitHub Issue
Medium 5.0 WS-2019-0019 #4

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 🌴

An in-range update of webpack-bundle-analyzer is breaking the build 🚨

The devDependency webpack-bundle-analyzer was updated from 3.1.0 to 3.2.0.

🚨 View failing branch.

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

webpack-bundle-analyzer 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
  • WhiteSource Security Check: The Security Check found 3 vulnerabilities.

Severity CVSS Score CVE GitHub Issue
Medium 5.0 WS-2019-0019 #4
Medium 5.0 [WS-2019-0032]( "Go to CVE Details") #15
Medium 5.0 [WS-2019-0047]( "Go to CVE Details") #21

Commits

The new version differs by 3 commits.

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 🌴

WS-2019-0047 Medium Severity Vulnerability detected by WhiteSource

WS-2019-0047 - Medium Severity Vulnerability

Vulnerable Library - tar-4.4.1.tgz

tar for node

path: null

Library home page: https://registry.npmjs.org/tar/-/tar-4.4.1.tgz

Dependency Hierarchy:

  • react-scripts-2.1.8.tgz (Root Library)
    • fsevents-1.2.4.tgz
      • node-pre-gyp-0.10.0.tgz
        • tar-4.4.1.tgz (Vulnerable Library)

Found in HEAD commit: 7d6c3cc20f81de03f185661539b9d4e935cd5391

Vulnerability Details

Versions of node-tar prior to 4.4.2 are vulnerable to Arbitrary File Overwrite. Extracting tarballs containing a hardlink to a file that already exists in the system, and a file that matches the hardlink will overwrite the system's file with the contents of the extracted file.

Publish Date: 2019-04-05

URL: WS-2019-0047

CVSS 2 Score Details (5.0)

Base Score Metrics not available

Suggested Fix

Type: Upgrade version

Origin: https://www.npmjs.com/advisories/803

Release Date: 2019-04-05

Fix Resolution: 4.4.2


Step up your Open Source Security Game with WhiteSource here

An in-range update of regenerator-runtime is breaking the build 🚨

The devDependency regenerator-runtime was updated from 0.13.1 to 0.13.2.

🚨 View failing branch.

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

regenerator-runtime 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
  • WhiteSource Security Check: The Security Check found 1 vulnerabilities.

Severity CVSS Score CVE GitHub Issue
Medium 5.0 WS-2019-0019 #4

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 🌴

An in-range update of nodemon is breaking the build 🚨

The dependency nodemon was updated from 1.18.11 to 1.19.0.

🚨 View failing branch.

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

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

Status Details

Release Notes for v1.19.0

1.19.0 (2019-05-01)

Bug Fixes

  • disable fork only if string starts with dash (886527f), closes #1554
  • Quote zero-length strings in arguments (#1551) (2973afb)

Features

Commits

The new version differs by 4 commits.

  • 20ccb62 feat: add message event
  • 886527f fix: disable fork only if string starts with dash
  • 64b474e feat: add TypeScript to default execPath (#1552)
  • 2973afb fix: Quote zero-length strings in arguments (#1551)

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 🌴

An in-range update of webpack-dev-server is breaking the build 🚨

The devDependency webpack-dev-server was updated from 3.3.1 to 3.4.0.

🚨 View failing branch.

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

webpack-dev-server 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
  • Travis CI - Branch: The build errored.
  • WhiteSource Security Check: Way to go! The Security Check did not find any vulnerabilities.

Release Notes for v3.4.0

3.4.0 (2019-05-17)

Bug Fixes

Features

Commits

The new version differs by 60 commits.

  • 45d39ac chore(release): 3.4.0
  • ec7eb9c chore(deps): update dependency internal-ip to ^4.3.0 (#1893)
  • dbb845d chore(renovate): ignore peerDependencies (#1894)
  • df9d09c chore(deps): update express to 4.17 version (#1896)
  • 2a81ad2 fix(stats): add errors-warnings preset (#1895)
  • ce3792c chore(deps): update all patch dependencies (patch) (#1892)
  • fc4fe32 feat(server): add liveReload option to enable/disable live reloading (#1889)
  • 1c2beff chore(renovate): add rangeStrategy: bump (#1885)
  • 6020e21 refactor: setupFeatures method (#1891)
  • df6a020 chore: refactor lint and prettier commands (#1888)
  • 2f56b18 chore(deps): update dependency eslint-config-prettier to v4.3.0 (#1887)
  • 294e155 refactor: listen method (#1884)
  • c535bb2 fix: do not include config files in dist (#1883)
  • fd0610b ci: npm audit and lint commit message (#1880)
  • d1c319c refactor: setupFeatures method (#1877)

There are 60 commits in total.

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 🌴

An in-range update of babel-plugin-transform-async-to-promises is breaking the build 🚨

The devDependency babel-plugin-transform-async-to-promises was updated from 0.8.6 to 0.8.7.

🚨 View failing branch.

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

babel-plugin-transform-async-to-promises 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
  • WhiteSource Security Check: The Security Check found 1 vulnerabilities.

Severity CVSS Score CVE GitHub Issue
Medium 5.0 WS-2019-0019 #4

Commits

The new version differs by 3 commits.

  • 909a6bb Public Release 0.8.7
  • 87d6782 Update dependencies
  • 0d10ebc Make each reference to a helper function a unique node so that babel 7's module import rewriting visitor won't skip rewriting some helpers

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 🌴

An in-range update of uglifyjs-webpack-plugin is breaking the build 🚨

The devDependency uglifyjs-webpack-plugin was updated from 2.1.2 to 2.1.3.

🚨 View failing branch.

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

uglifyjs-webpack-plugin 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
  • WhiteSource Security Check: Way to go! The Security Check did not find any vulnerabilities.
  • Travis CI - Branch: The build errored.

Release Notes for v2.1.3

2.1.3 (2019-05-15)

Bug Fixes

Commits

The new version differs by 4 commits.

  • 4c9abe6 chore(release): 2.1.3
  • 7619736 fix: disable parallel on WSL (#403)
  • 51ee60e chore(defaults): update (#402)
  • d117827 fix: fallback for cache directory (#401)

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 🌴

Action required: Greenkeeper could not be activated 🚨

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

An in-range update of enzyme is breaking the build 🚨

There have been updates to the enzyme monorepo:

    • The devDependency enzyme was updated from 3.8.0 to 3.9.0.

🚨 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 enzyme group definition.

enzyme 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

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 🌴

An in-range update of enzyme is breaking the build 🚨

There have been updates to the enzyme monorepo:

    • The devDependency enzyme was updated from 3.8.0 to 3.9.0.

🚨 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 enzyme group definition.

enzyme 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
  • WhiteSource Security Check: The Security Check found 2 vulnerabilities.

Severity CVSS Score CVE GitHub Issue
Medium 5.0 WS-2019-0019 #4
Medium 5.0 [WS-2019-0032]( "Go to CVE Details") #15

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 🌴

An in-range update of webpack is breaking the build 🚨

The devDependency webpack was updated from 4.30.0 to 4.31.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.

Status Details
  • Travis CI - Branch: The build errored.
  • WhiteSource Security Check: Way to go! The Security Check did not find any vulnerabilities.

Release Notes for v4.31.0

Features

  • add errors-warnings stats preset

Bugfixes

  • allow top-level return in non-ESM modules
Commits

The new version differs by 23 commits.

  • 2e1e179 4.31.0
  • b17543e Merge pull request #8919 from vincentrodriguez/errors-and-warnings-only-preset
  • fed4c3d Merge pull request #8985 from webpack/dependabot/npm_and_yarn/react-dom-16.8.6
  • d05435c Merge pull request #9062 from webpack/dependabot/npm_and_yarn/eslint-plugin-jest-22.5.1
  • 8bf8b82 Merge pull request #9066 from webpack/dependabot/npm_and_yarn/eslint-config-prettier-4.2.0
  • 00d0038 Merge pull request #9096 from webpack/dependabot/npm_and_yarn/glob-7.1.4
  • dbd856e Merge pull request #9098 from webpack/dependabot/npm_and_yarn/simple-git-1.113.0
  • 13045f1 chore(deps-dev): bump simple-git from 1.110.0 to 1.113.0
  • 5800043 chore(deps-dev): bump glob from 7.1.3 to 7.1.4
  • 084ca0b chore(deps-dev): bump eslint-config-prettier from 4.1.0 to 4.2.0
  • 022d1b7 chore(deps-dev): bump eslint-plugin-jest from 22.4.1 to 22.5.1
  • 81cf088 Merge pull request #9046 from mwijngaard/master
  • dc6dd51 Allow top-level return in script parsing. Fixes issue 8509 in master, like PR 8510 fixed it for 'next'
  • 42db81a Merge pull request #9029 from EugeneHlushko/mode/warning
  • 84ca105 mode(warning) update mode warning snapshot hash

There are 23 commits in total.

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 🌴

Invalid Greenkeeper configuration file

We have detected a problem with your Greenkeeper config file 🚨

Greenkeeper currently can’t work with your greenkeeper.json config file because it is invalid. We found the following issues:

  1. The package path examples/basic-react-example[map-with-key]/package.json in the group default is invalid. It must be a relative path to a package.json file. The path may not start with a slash, and it must end in package.json. Allowed characters for a path are alphanumeric, underscores, dashes, periods and the @ symbol (a-zA-Z_-.@).
  2. The package path examples/basic-redux-example[redux-promise]/package.json in the group default is invalid. It must be a relative path to a package.json file. The path may not start with a slash, and it must end in package.json. Allowed characters for a path are alphanumeric, underscores, dashes, periods and the @ symbol (a-zA-Z_-.@).
  3. The package path examples/basic-redux-example[redux-thunk]/package.json in the group default is invalid. It must be a relative path to a package.json file. The path may not start with a slash, and it must end in package.json. Allowed characters for a path are alphanumeric, underscores, dashes, periods and the @ symbol (a-zA-Z_-.@).
  4. The package path examples/basic-webpack[default]/package.json in the group default is invalid. It must be a relative path to a package.json file. The path may not start with a slash, and it must end in package.json. Allowed characters for a path are alphanumeric, underscores, dashes, periods and the @ symbol (a-zA-Z_-.@).

Please correct these and commit the fix to your default branch (usually master). Greenkeeper will pick up your changes and try again. If in doubt, please consult the config documentation.

Here’s an example of a valid greenkeeper.json:

{
  "groups": {
    "frontend": {
      "packages": [
        "webapp/package.json",
        "cms/package.json",
        "analytics/package.json"
      ]
    },
    "build": {
      "packages": [
        "package.json"
      ]
    }
  },
  "ignore": [
    "standard",
    "eslint"
  ]
}

This files tells Greenkeeper to handle all dependency updates in two groups. All files in the frontend group will receive updates together, in one issue or PR, and the root-level package.json in the build group will be treated separately. In addition, Greenkeeper will never send updates for the standard and eslint packages.

🤖 🌴

An in-range update of body-parser is breaking the build 🚨

The dependency body-parser was updated from 1.18.3 to 1.19.0.

🚨 View failing branch.

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

body-parser 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.

Status Details
  • Travis CI - Branch: The build errored.
  • WhiteSource Security Check: Way to go! The Security Check did not find any vulnerabilities.

Commits

The new version differs by 44 commits.

There are 44 commits in total.

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 🌴

An in-range update of emotion is breaking the build 🚨

There have been updates to the emotion monorepo:

    • The dependency @emotion/core was updated from 10.0.9 to 10.0.10.

🚨 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 emotion group definition.

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

Status Details
  • Travis CI - Branch: The build errored.
  • WhiteSource Security Check: Way to go! The Security Check did not find any vulnerabilities.

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 🌴

An in-range update of webpack-merge is breaking the build 🚨

The devDependency webpack-merge was updated from 4.2.1 to 4.2.2.

🚨 View failing branch.

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

webpack-merge 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
  • WhiteSource Security Check: Oops! An error occurred while running the Security Check.

Please contact the WhiteSource Support team at [email protected] and mention the following scan token: 13c2608dfbeb480a91ea292528f2d002

Commits

The new version differs by 7 commits.

  • d35e176 4.2.2
  • a53214d Update lib
  • ec35567 chore: Update changelog
  • a56d5cb chore(merge): Update lodash to avoid npm audit warning
  • ef4c067 docs(merge): Improve merge.unique docs
  • ad2f92a docs(readme): Add a note about precedence
  • c3a5156 chore: Add @desfero to contributors

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 🌴

WS-2019-0034 Medium Severity Vulnerability detected by WhiteSource

WS-2019-0034 - Medium Severity Vulnerability

Vulnerable Libraries - js-yaml-3.12.0.tgz, js-yaml-3.12.2.tgz

js-yaml-3.12.0.tgz

YAML 1.2 parser and serializer

path: null

Library home page: https://registry.npmjs.org/js-yaml/-/js-yaml-3.12.0.tgz

Dependency Hierarchy:

  • styled-10.0.5.tgz (Root Library)
    • babel-plugin-emotion-10.0.5.tgz
      • babel-plugin-macros-2.4.3.tgz
        • cosmiconfig-5.0.7.tgz
          • js-yaml-3.12.0.tgz (Vulnerable Library)
js-yaml-3.12.2.tgz

YAML 1.2 parser and serializer

path: /tmp/git/react/basic-react-example[map-with-key]/node_modules/js-yaml/package.json

Library home page: https://registry.npmjs.org/js-yaml/-/js-yaml-3.12.2.tgz

Dependency Hierarchy:

  • react-scripts-2.1.8.tgz (Root Library)
    • eslint-5.12.0.tgz
      • js-yaml-3.12.2.tgz (Vulnerable Library)

Found in HEAD commit: 45e8e7d96aa6466ec2d01245e6fbe62d5bc895f7

Vulnerability Details

Versions js-yaml prior to 3.13.0 are vulnerable to Denial of Service. By parsing a carefully-crafted YAML file, the node process stalls and may exhaust system resources leading to a Denial of Service.

Publish Date: 2019-03-31

URL: WS-2019-0034

CVSS 2 Score Details (5.0)

Base Score Metrics not available

Suggested Fix

Type: Upgrade version

Origin: https://www.npmjs.com/advisories/788

Release Date: 2019-03-31

Fix Resolution: 3.13.0


Step up your Open Source Security Game with WhiteSource here

An in-range update of enzyme is breaking the build 🚨

There have been updates to the enzyme monorepo:

    • The devDependency enzyme was updated from 3.8.0 to 3.9.0.

🚨 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 enzyme group definition.

enzyme 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
  • Travis CI - Branch: The build errored.
  • WhiteSource Security Check: Way to go! The Security Check did not find any vulnerabilities.

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 🌴

An in-range update of emotion is breaking the build 🚨

There have been updates to the emotion monorepo:

    • The dependency @emotion/core was updated from 10.0.9 to 10.0.10.

🚨 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 emotion group definition.

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

Status Details
  • WhiteSource Security Check: The Security Check found 1 vulnerabilities.

Severity CVSS Score CVE GitHub Issue
Medium 5.0 WS-2019-0019 #4

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 🌴

An in-range update of enzyme is breaking the build 🚨

There have been updates to the enzyme monorepo:

    • The devDependency enzyme was updated from 3.8.0 to 3.9.0.

🚨 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 enzyme group definition.

enzyme 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
  • WhiteSource Security Check: Way to go! The Security Check did not find any vulnerabilities.
  • Travis CI - Branch: The build errored.

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 🌴

An in-range update of webpack-dev-middleware is breaking the build 🚨

The devDependency webpack-dev-middleware was updated from 3.6.2 to 3.7.0.

🚨 View failing branch.

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

webpack-dev-middleware 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
  • WhiteSource Security Check: Way to go! The Security Check did not find any vulnerabilities.
  • Travis CI - Branch: The build errored.

Release Notes for v3.7.0

3.7.0 (2019-05-15)

Features

Commits

The new version differs by 11 commits.

  • 81bc1f7 chore(release): 3.7.0
  • ef38424 chore(deps): update dependency lint-staged to v8.1.7 (#402)
  • ec3d5eb feat: support HEAD method by default (#398)
  • f227570 chore(deps): update dependency prettier to v1.17.1 (#400)
  • 839e7a7 chore(deps): update dependency husky to v2.3.0 (#401)
  • db50233 chore(deps): pin dependencies (#396)
  • 036186e chore(renovate): update config file (#397)
  • af94704 chore(default): migrate (#394)
  • 762efe4 Configure Renovate (#395)
  • 6d191d0 chore(deps): update some devDependencies (#389)
  • e1c160b chore(github): add hiroppy to CODEOWNERS (#388)

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 🌴

An in-range update of enzyme is breaking the build 🚨

There have been updates to the enzyme monorepo:

    • The devDependency enzyme was updated from 3.8.0 to 3.9.0.

🚨 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 enzyme group definition.

enzyme 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
  • WhiteSource Security Check: The Security Check found 3 vulnerabilities.

Severity CVSS Score CVE GitHub Issue
Medium 5.0 WS-2019-0019 #4
Medium 5.0 [WS-2019-0032]( "Go to CVE Details") #15
Medium 5.0 [WS-2019-0047]( "Go to CVE Details") #21

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 🌴

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

    • The devDependency @babel/core was updated from 7.5.0 to 7.5.4.

🚨 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 babel7 group definition.

babel7 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
  • WhiteSource Security Check: Oops! An error occurred while running the Security Check.

Please contact [email protected] and mention the following support token: a7f83a81d75c4063bbc3e41d61a3eb3b

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 🌴

An in-range update of webpack-hot-middleware is breaking the build 🚨

The devDependency webpack-hot-middleware was updated from 2.24.3 to 2.24.4.

🚨 View failing branch.

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

webpack-hot-middleware 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
  • Travis CI - Branch: The build errored.
  • WhiteSource Security Check: Way to go! The Security Check did not find any vulnerabilities.

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 🌴

An in-range update of enzyme is breaking the build 🚨

There have been updates to the enzyme monorepo:

    • The devDependency enzyme was updated from 3.8.0 to 3.9.0.

🚨 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 enzyme group definition.

enzyme 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
  • Travis CI - Branch: The build errored.
  • WhiteSource Security Check: Way to go! The Security Check did not find any vulnerabilities.

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 🌴

An in-range update of webpack-dev-middleware is breaking the build 🚨

The devDependency webpack-dev-middleware was updated from 3.6.1 to 3.6.2.

🚨 View failing branch.

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

webpack-dev-middleware 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
  • WhiteSource Security Check: The Security Check found 2 vulnerabilities.

Severity CVSS Score CVE GitHub Issue
Medium 5.0 WS-2019-0019 #4
Medium 5.0 [WS-2019-0032]( "Go to CVE Details") #15

Release Notes for v3.6.2

3.6.2 (2019-04-03)

Bug Fixes

  • check existence of res.getHeader and set the correct Content-Type (#385) (56dc705)
Commits

The new version differs by 5 commits.

  • 7942228 chore(release): 3.6.2
  • 56dc705 fix: check existence of res.getHeader and set the correct Content-Type (#385)
  • eb2e32b chore: import development (#387)
  • e6c2b3c refactor: migrate on jest (#386)
  • dba5e02 test: fix overwrite Content-Type (#378)

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 🌴

CVE-2018-3728 Medium Severity Vulnerability detected by WhiteSource

CVE-2018-3728 - Medium Severity Vulnerability

Vulnerable Library - hoek-4.2.1.tgz

General purpose node utilities

path: /tmp/git/react/basic-redux-example[redux-thunk]/node_modules/hoek/package.json

Library home page: https://registry.npmjs.org/hoek/-/hoek-4.2.1.tgz

Dependency Hierarchy:

  • react-scripts-2.1.1.tgz (Root Library)
    • workbox-webpack-plugin-3.6.3.tgz
      • workbox-build-3.6.3.tgz
        • joi-11.4.0.tgz
          • hoek-4.2.1.tgz (Vulnerable Library)

Vulnerability Details

hoek node module before 4.2.0 and 5.0.x before 5.0.3 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via 'merge' and 'applyToDefaults' functions, which allows a malicious user to modify the prototype of "Object" via proto, causing the addition or modification of an existing property that will exist on all objects.

Publish Date: 2018-03-30

URL: CVE-2018-3728

CVSS 3 Score Details (6.5)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Network
    • Attack Complexity: Low
    • Privileges Required: Low
    • User Interaction: None
    • Scope: Unchanged
  • Impact Metrics:
    • Confidentiality Impact: None
    • Integrity Impact: High
    • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Change files

Origin: hapijs/hoek@623667e

Release Date: 2018-02-15

Fix Resolution: Replace or update the following files: index.js, index.js


Step up your Open Source Security Game with WhiteSource here

An in-range update of lodash is breaking the build 🚨

The dependency lodash was updated from 4.17.11 to 4.17.12.

🚨 View failing branch.

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

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

Status Details
  • WhiteSource Security Check: Oops! An error occurred while running the Security Check.

Please contact [email protected] and mention the following support token: e7b62fbdbb844a1cb953bce6192a100c

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 🌴

An in-range update of babel-plugin-transform-async-to-promises is breaking the build 🚨

The devDependency babel-plugin-transform-async-to-promises was updated from 0.8.9 to 0.8.10.

🚨 View failing branch.

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

babel-plugin-transform-async-to-promises 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
  • WhiteSource Security Check: Way to go! The Security Check did not find any vulnerabilities.
  • Travis CI - Branch: The build errored.

Commits

The new version differs by 5 commits.

  • b3b6e48 Public Release 0.8.10
  • 9075716 Package helpers in helpers-string.js as a commonjs module so that bundlers may include it as content
  • 1a23976 Commit results of npm audit fix
  • ef509f6 Update dependencies
  • 39e7bb8 Support default parameters internally so that exceptions are converted to a rejected Promise and so that it doesn't interfere with babel's rewriting passes (closes #28)

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 🌴

An in-range update of dotenv is breaking the build 🚨

The dependency dotenv was updated from 8.1.0 to 8.2.0.

🚨 View failing branch.

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

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

Status Details
  • WhiteSource Security Check: Oops! An error occurred while running the Security Check.

Please contact the WhiteSource Support team at [email protected] and mention the following scan token: 464aee6856ae4ec0920064861ef56ba6

Commits

The new version differs by 3 commits.

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 🌴

An in-range update of enzyme is breaking the build 🚨

There have been updates to the enzyme monorepo:

    • The devDependency enzyme was updated from 3.8.0 to 3.9.0.

🚨 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 enzyme group definition.

enzyme 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
  • WhiteSource Security Check: The Security Check found 3 vulnerabilities.

Severity CVSS Score CVE GitHub Issue
Medium 5.0 WS-2019-0019 #4
Medium 5.0 [WS-2019-0032]( "Go to CVE Details") #15
Medium 5.0 [WS-2019-0047]( "Go to CVE Details") #21

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 🌴

WS-2019-0019 Medium Severity Vulnerability detected by WhiteSource

WS-2019-0019 - Medium Severity Vulnerability

Vulnerable Library - braces-1.8.5.tgz

Fastest brace expansion for node.js, with the most complete support for the Bash 4.3 braces specification.

path: /tmp/git/react/basic-redux-example[redux-thunk]/node_modules/braces/package.json,/tmp/git/react/react-redux-webpack-client/node_modules/jest/node_modules/braces/package.json,/tmp/git/react/basic-react-example[map-with-key]/node_modules/braces/package.json,/tmp/git/react/basic-redux-example[redux-promise]/node_modules/braces/package.json

Library home page: https://registry.npmjs.org/braces/-/braces-1.8.5.tgz

Dependency Hierarchy:

  • jest-23.6.0.tgz (Root Library)
    • jest-cli-23.6.0.tgz
      • micromatch-2.3.11.tgz
        • braces-1.8.5.tgz (Vulnerable Library)

Vulnerability Details

Version of braces prior to 2.3.1 are vulnerable to Regular Expression Denial of Service (ReDoS). Untrusted input may cause catastrophic backtracking while matching regular expressions. This can cause the application to be unresponsive leading to Denial of Service.

Publish Date: 2019-02-21

URL: WS-2019-0019

CVSS 2 Score Details (5.0)

Base Score Metrics not available

Suggested Fix

Type: Upgrade version

Origin: https://www.npmjs.com/advisories/786

Release Date: 2019-02-21

Fix Resolution: 2.3.1


Step up your Open Source Security Game with WhiteSource here

An in-range update of enzyme is breaking the build 🚨

There have been updates to the enzyme monorepo:

    • The devDependency enzyme was updated from 3.8.0 to 3.9.0.

🚨 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 enzyme group definition.

enzyme 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
  • Travis CI - Branch: The build errored.
  • WhiteSource Security Check: Way to go! The Security Check did not find any vulnerabilities.

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 🌴

An in-range update of babel-loader is breaking the build 🚨

The devDependency babel-loader was updated from 8.0.5 to 8.0.6.

🚨 View failing branch.

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

babel-loader 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
  • WhiteSource Security Check: Way to go! The Security Check did not find any vulnerabilities.
  • Travis CI - Branch: The build errored.

Release Notes for 8.0.6
  • Migrate to pify (#785)
  • Reduced memory usage (#781)
Commits

The new version differs by 11 commits.

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 🌴

An in-range update of nodemon is breaking the build 🚨

The dependency nodemon was updated from 1.18.10 to 1.18.11.

🚨 View failing branch.

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

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

Status Details
  • WhiteSource Security Check: The Security Check found 3 vulnerabilities.

Severity CVSS Score CVE GitHub Issue
Medium 5.0 WS-2019-0019 #4
Medium 5.0 [WS-2019-0047]( "Go to CVE Details") #21
Medium 5.0 [WS-2019-0032]( "Go to CVE Details") #15

Release Notes for v1.18.11

1.18.11 (2019-04-08)

Bug Fixes

Commits

The new version differs by 1 commits.

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 🌴

Invalid Greenkeeper configuration file

We have detected a problem with your Greenkeeper config file 🚨

Greenkeeper currently can’t work with your greenkeeper.json config file because it is invalid. We found the following issues:

  1. The package path basic-react-example[map-with-key]/package.json in the group default is invalid. It must be a relative path to a package.json file. The path may not start with a slash, and it must end in package.json. Allowed characters for a path are alphanumeric, underscores, dashes, periods and the @ symbol (a-zA-Z_-.@).
  2. The package path basic-redux-example[redux-promise]/package.json in the group default is invalid. It must be a relative path to a package.json file. The path may not start with a slash, and it must end in package.json. Allowed characters for a path are alphanumeric, underscores, dashes, periods and the @ symbol (a-zA-Z_-.@).
  3. The package path basic-redux-example[redux-thunk]/package.json in the group default is invalid. It must be a relative path to a package.json file. The path may not start with a slash, and it must end in package.json. Allowed characters for a path are alphanumeric, underscores, dashes, periods and the @ symbol (a-zA-Z_-.@).
  4. The package path basic-webpack[default]/package.json in the group default is invalid. It must be a relative path to a package.json file. The path may not start with a slash, and it must end in package.json. Allowed characters for a path are alphanumeric, underscores, dashes, periods and the @ symbol (a-zA-Z_-.@).

Please correct these and commit the fix to your default branch (usually master). Greenkeeper will pick up your changes and try again. If in doubt, please consult the config documentation.

Here’s an example of a valid greenkeeper.json:

{
  "groups": {
    "frontend": {
      "packages": [
        "webapp/package.json",
        "cms/package.json",
        "analytics/package.json"
      ]
    },
    "build": {
      "packages": [
        "package.json"
      ]
    }
  },
  "ignore": [
    "standard",
    "eslint"
  ]
}

This files tells Greenkeeper to handle all dependency updates in two groups. All files in the frontend group will receive updates together, in one issue or PR, and the root-level package.json in the build group will be treated separately. In addition, Greenkeeper will never send updates for the standard and eslint packages.

🤖 🌴

An in-range update of webpack-cli is breaking the build 🚨

The devDependency webpack-cli was updated from 3.3.0 to 3.3.1.

🚨 View failing branch.

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

webpack-cli 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
  • Travis CI - Branch: The build errored.
  • WhiteSource Security Check: Way to go! The Security Check did not find any vulnerabilities.

Commits

The new version differs by 74 commits.

  • d3f8e20 chore: v.3.1.1
  • f371e72 Merge pull request #847 from anshumanv/846
  • da9e732 Merge pull request #841 from pranshuchittora/docs-remove
  • cb68b1b docs(serve): link to webpack-dev-server
  • f7451d4 docs(serve): update docs to use webpack-dev-server
  • 06b4929 Remove tslint in favour of eslint (#834)
  • 8c1db03 chore(docs): removes scaffolding docs from the root
  • dc941e6 docs(contributing): fixes dead link (#835)
  • b8d5511 Merge pull request #832 from pranshuchittora/docs
  • 6a0375a docs(packages): adds downloads/month shield
  • 963c85f Merge pull request #818 from pranshuchittora/refactor-utils
  • 8506ccf Merge pull request #827 from rishabh3112/patch-9
  • 6816057 chore(deps): upgrade lerna to fix vulnerabilities & update webpack-dev-server (#823)
  • 834d90e Merge pull request #828 from pranshuchittora/shields
  • 958d064 docs(readme): adds contributors shield

There are 74 commits in total.

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 🌴

An in-range update of enzyme is breaking the build 🚨

There have been updates to the enzyme monorepo:

    • The devDependency enzyme was updated from 3.8.0 to 3.9.0.

🚨 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 enzyme group definition.

enzyme 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

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 🌴

An in-range update of webpack is breaking the build 🚨

The devDependency webpack was updated from 4.29.6 to 4.30.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.

Status Details
  • WhiteSource Security Check: The Security Check found 3 vulnerabilities.

Severity CVSS Score CVE GitHub Issue
Medium 5.0 WS-2019-0019 #4
Medium 5.0 [WS-2019-0047]( "Go to CVE Details") #21
Medium 5.0 [WS-2019-0032]( "Go to CVE Details") #15

Release Notes for v4.30.0

Features

  • add amd: false to disable AMD support
  • Compilation.hooks.finishModules now also allows async plugins
  • add output.libraryTarget: "system" to compile for SystemJs environment

Bugfixes

  • fix generating a null id when concatenating an entry module in a different chunk
  • fix unneeded chunk references when splitting modules from chunks
  • fix parsing of function name in function scope

Performance

  • Lazy require some internal files
  • Faster way to generate function headers

Contributing

  • Run prettier on examples markdown
Commits

The new version differs by 102 commits.

  • b72b96a 4.30.0
  • 9ededfa Merge pull request #9034 from webpack/dependabot/npm_and_yarn/tapable-1.1.3
  • e33a91f chore(deps): bump tapable from 1.1.1 to 1.1.3
  • de81dd0 Merge pull request #8864 from joeldenning/issue-8833
  • 7dfddc2 Merge pull request #8858 from webpack/dependabot/npm_and_yarn/json-schema-to-typescript-6.1.3
  • f7d0c25 Improve way how System is tested
  • 39a680d formating of output code
  • e2e74f5 Merge pull request #8980 from webpack/dependabot/npm_and_yarn/eslint-5.16.0
  • 81dc70d Merge pull request #9022 from sandersn/fix-webassembly-declaration
  • 13aa512 Merge pull request #9023 from webpack/dependabot/npm_and_yarn/typescript-3.4.3
  • 1566036 chore(deps-dev): bump typescript from 3.4.2 to 3.4.3
  • ce33ca7 Update WebAssembly declaration
  • 5117461 Merge pull request #9006 from hiroppy/feature/fix-template-syntax
  • 9e60850 Merge pull request #8984 from webpack/dependabot/npm_and_yarn/react-16.8.6
  • 5f75527 Bump json-schema-to-typescript from 6.1.1 to 6.1.3

There are 102 commits in total.

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 🌴

An in-range update of react-redux is breaking the build 🚨

The dependency react-redux was updated from 7.0.2 to 7.0.3.

🚨 View failing branch.

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

react-redux 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.

Status Details

Commits

The new version differs by 12 commits.

  • dbfcc97 7.0.3
  • d162625 fix timing issue in component updates due to consecutive dispatches (#1263)
  • 9803028 Remove unnecessary import from hooks docs (#1258)
  • 67944a3 Fix error in docs for useSelector (#1255)
  • e2804f2 Fix typo in useSelector docs (#1254)
  • d4f09a7 Add selector deps, perf info, and bump version (#1253)
  • aefc520 Fix example typo (#1250)
  • cf24fc8 Fix React hooks API links
  • edc1501 Hooks docs (#1249)
  • d4b54b5 Lower react peer dependency to ^16.8.3 (#1242)
  • b67a8d3 Fix broken link (#1243)
  • 960b733 Bumped required React version in documentation (#1238)

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 🌴

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

    • The devDependency @babel/core was updated from 7.3.4 to 7.4.0.

🚨 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 babel7 group definition.

babel7 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
  • WhiteSource Security Check: The Security Check found 1 vulnerabilities.

Severity CVSS Score CVE GitHub Issue
Medium 5.0 WS-2019-0019 #4

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 🌴

An in-range update of webpack-dev-server is breaking the build 🚨

The devDependency webpack-dev-server was updated from 3.2.1 to 3.3.0.

🚨 View failing branch.

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

webpack-dev-server 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
  • WhiteSource Security Check: The Security Check found 3 vulnerabilities.

Severity CVSS Score CVE GitHub Issue
Medium 5.0 WS-2019-0019 #4
Medium 5.0 [WS-2019-0032]( "Go to CVE Details") #15
Medium 5.0 [WS-2019-0047]( "Go to CVE Details") #21

Release Notes for v3.3.0

3.3.0 (2019-04-08)

Bug Fixes

Features

  • add option "serveIndex" to enable/disable serveIndex middleware (#1752) (d5d60cb)
  • add webpack as argument to before and after options (#1760) (0984d4b)
  • http2 option to enable/disable HTTP/2 with HTTPS (#1721) (dcd2434)
  • random port retry logic (#1692) (419f02e)
  • relax depth limit from chokidar for content base (#1697) (7ea9ab9)
Commits

The new version differs by 34 commits.

  • 99e8db0 chore(release): 3.3.0
  • df3ee67 test: refactor (#1768)
  • f61dfd4 test: compress option (#1766)
  • 919ff77 fix(Server): validate express.static.mime.types (#1765)
  • 1b3cd4f chore(deps): update dependency marked to v0.6.2 (#1764)
  • d5d60cb feat: add option "serveIndex" to enable/disable serveIndex middleware (#1752)
  • abf8691 Pass mimeTypes option to webpack-dev-middleware (#1714)
  • 05b8fb7 style: add curly rule to eslint (#1761)
  • dcd2434 feat: http2 option to enable/disable HTTP/2 with HTTPS (#1721)
  • 0984d4b feat: add webpack as argument to before and after options (#1760)
  • 31dfe22 chore(deps): update (#1759)
  • 737171e chore(deps): update dependency supertest to v4 (#1757)
  • 0429113 chore(deps): update all minor dependencies (#1756)
  • 5b55110 chore(deps): update all patch dependencies (patch) (#1755)
  • e65705b chore(deps): pin dependencies (#1705)

There are 34 commits in total.

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 🌴

An in-range update of clean-webpack-plugin is breaking the build 🚨

The devDependency clean-webpack-plugin was updated from 2.0.1 to 2.0.2.

🚨 View failing branch.

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

clean-webpack-plugin 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
  • WhiteSource Security Check: Way to go! The Security Check did not find any vulnerabilities.
  • Travis CI - Branch: The build errored.

Commits

The new version differs by 7 commits.

  • 9e23e7b bumped version to 2.0.2
  • 5415087 Merge pull request #137 from chrisblossom/options-partial
  • 18f71a5 replace Partial with explicit optional options
  • 4f8ae44 Merge pull request #135 from chrisblossom/export-options
  • b9b35f8 export Options type
  • 9f8a3bb Merge pull request #113 from mkungla/patch-1
  • 8fbf1f4 Remove duplicate dry from readme

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 🌴

An in-range update of jest-watch-typeahead is breaking the build 🚨

The devDependency jest-watch-typeahead was updated from 0.3.0 to 0.3.1.

🚨 View failing branch.

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

jest-watch-typeahead 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
  • WhiteSource Security Check: Way to go! The Security Check did not find any vulnerabilities.
  • Travis CI - Branch: The build errored.

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 🌴

An in-range update of express is breaking the build 🚨

The dependency express was updated from 4.16.4 to 4.17.0.

🚨 View failing branch.

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

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

Status Details
  • Travis CI - Branch: The build errored.
  • WhiteSource Security Check: Way to go! The Security Check did not find any vulnerabilities.

Release Notes for 4.17.0
Commits

The new version differs by 53 commits.

There are 53 commits in total.

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 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.