There have been updates to the babel7 monorepo:

• • The devDependency @babel/core was updated from 7.4.3 to 7.4.4.

• The devDependency @babel/preset-env was updated from 7.4.3 to 7.4.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.

Your Greenkeeper Bot 🌴

The devDependency eslint-plugin-jest was updated from 22.3.0 to 22.3.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-jest 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 🌴

https://github.com/flowtype/flow-typed

This lib doesn't handle JavaScript Maps, correct?

var equal = require("shallowequal")

var a = { name: 'fraserxu', belongs: ['bike', 'mac'] }
var b = { belongs: ['bike', 'mac'], name: 'fraserxu' }
var c = { belongs: ['bike', 'mac'], name: 'fraserxu' }

console.log(equal(a, b)) // false
console.log(equal(b, c)) // false

but if I use substack's node-deep-equal

var equal = require("deep-equal")

var a = { name: 'fraserxu', belongs: ['bike', 'mac'] }
var b = { belongs: ['bike', 'mac'], name: 'fraserxu' }
var c = { belongs: ['bike', 'mac'], name: 'fraserxu' }

console.log(equal(a, b)) // true
console.log(equal(b, c)) // true

Is this the desired behaviour of shallowEqual? Sorry this is not an issue but I'm curious about the difference between deep and shallow here.

Getting the following error

Error: Couldn't find preset "es2015" relative to directory "/Users/<username>/Projects/<project-name>/node_modules/shallowequal"

I'm using babel-preset-env and not es2015

I am currently working with Meteor and we use PureRenderMixin to render or not when properties change. Facebook released an update to use shallowCompare mixin which makes use of shallowequal and this has a dependency to lodash.keys. Meteor however applies Underscore and I would love to utilize it more often if possible. But to be more dependency free, would shallowequal work with Object.keys? It seems to apply the same logic and return an array of keys.

Update: Object.keys is not working on IE-version lower than 9. But there are polyfills.

For example,
const objA = {data: [1,2,3]}; const objB = {data: [1,2,3]}; console.log(shallowEqual(objA, objB); // => false

The devDependency eslint was updated from 5.15.3 to 5.16.0.

🚨 View failing branch.

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

eslint 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 🌴

Essentially replace mocha and chai with jest.

The devDependency eslint-plugin-jest was updated from 22.5.1 to 22.6.0.

🚨 View failing branch.

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

eslint-plugin-jest 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 🌴

Update docs to contrast with API semantics of lodash v4 _.isEqualWith. This is equivalent to v3 _.isEqual.

See: https://github.com/lodash/lodash/wiki/Changelog#jan-12-2016--diff--docs

🚨 You need to enable Continuous Integration on all 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 we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

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

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

node v6 will reach end-of-life on April 2019: https://github.com/nodejs/Release#release-schedule

Uglify does not support let statements. Due to the recent release many webpack production builds are failing because of this.

https://github.com/facebook/flow/releases/tag/v0.89.0

We've deleted flow gen-flow-files due to bitrot. We do plan on building a better version in the future.

Figure out the flow gen-flow-files situation.

Related PR: #49

This issue provides visibility into Renovate updates and their statuses. Learn more

Rate Limited

These updates are currently rate limited. Click on a checkbox below to force their creation now.

• Update dependency husky to v7

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update babel monorepo to v7.15.8 (@babel/core, @babel/preset-env)
• Update dependency eslint-plugin-jest to v23.20.0
• Update dependency flow-bin to v0.162.0
• Update dependency lint-staged to v10.5.4
• Update jest monorepo (babel-jest, jest)
• Update dependency eslint to v8
• Update dependency eslint-plugin-jest to v25
• Update dependency lint-staged to v11
• Update dependency prettier to v2
• Update jest monorepo to v27 (major) (babel-jest, jest)
• Click on this checkbox to rebase all open PRs at once

• Check this box to trigger a request for Renovate to run again on this repository

The devDependency flow-bin was updated from 0.98.0 to 0.98.1.

🚨 View failing branch.

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

flow-bin 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 🌴

https://www.npmjs.com/package/@types/shallowequal

Prefer Object.is over strict equality.

See: facebook/fbjs#102