Automate dependency maintenance.

[ericelliott]

After this PR, we'll want to turn on Greenkeeper.io.

└[∵┌]└[ ∵ ]┘[┐∵]┘

[svenheden]

👍

[ericelliott]

This PR has 4 major version bumps that need to be investigated more carefully by somebody more familiar with the code.

(☞ﾟ∀ﾟ)☞ @JedWatson

[JedWatson]

Two things to call out:

• multer currently needs to be pinned at 0.1.8 (see Update Multer #1563)
• qs needs to be pinned at 4.0.0, this is aligned with the dependency in history.

qs is basically (╯°□°)╯︵ ┻━┻

they've migrated the package to es6 without shipping a transpiled build, which means we would need to change our build process to babelify it ourselves and use in node.js would break compatibility with 0.10/12 which Keystone still currently targets.

So for that, and to prevent duplicates in the client-side bundle (w/ history), we're leaving it where it is until there's a better option. I'd like to move away from it entirely.

I haven't tested babel-eslint@5.0.0-beta4 but I expect we can work through any issues that come up (if any)

Everything else looks 👍

[ericelliott]

they've migrated the package to es6 without shipping a transpiled build, which means we would need to change our build process to babelify it ourselves and use in node.js would break compatibility with 0.10/12 which Keystone still currently targets.

We should file this as a bug against their repo.

[ericelliott]

I haven't tested babel-eslint@5.0.0-beta4

I found a bug in this today. I'm going to re-pin an older version.

[JedWatson]

Good to go! Thanks @ericelliott

[JedWatson]

We should file this as a bug against their repo.

From issues I've already read, they're aware and don't care. The whole project has had a call for maintainers. It also looks like client side support is being dropped, based on a thread on the history repo (where we're discussing moving to a different package)

[ericelliott]

Is there an issue tracking the replacement?

[JedWatson]

@ericelliott remix-run/history#121

[ericelliott]

👍