Update history to version 4.2.0 🚀

[greenkeeperio-bot]

Hello lovely humans,

history just published its new version 4.2.0.

State	Update 🚀
Dependency	history
New version	4.2.0
Type	dependency

This version is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of history.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴

---

The new version differs by 214 commits (ahead by 214, behind by 20).

• b37e9c8 Version 4.2.0
• 637aa0c Update CHANGES
• 913bd10 Add createLocation to top-level exports
• 5d2364f Inline warning
• 8450e07 Version 4.1.0
• a263d43 Update CHANGES
• 021c9ba Automatically clean up bad location descriptors
• 100e6dd Use a leading / when doing history.push('')
• 1d0d6a0 Update release script
• 7074a3a Version 4.0.1
• 4f7687e Update package description
• 1fd82f4 Update README
• e874df6 chore(package): update babel-preset-es2015-loose to version 8.0.0 (#363)
• 399c72c Version 4.0.0
• 686925c Update CHANGES

There are 214 commits in total. See the full diff.

---

This pull request was created by greenkeeper.io.

_{Tired of seeing this sponsor message? ⚡ greenkeeper upgrade}

[coveralls]

Coverage remained the same at 92.378% when pulling cdca030 on greenkeeper-history-4.2.0 into 999e2c6 on master.

[Mardak]

Normally I would close this referring to #1267, but the builds here are incorrectly green. I believe @piatra has said these should actually be failing, so it seems like something bad is going on with the "false green" builds.

@k88hudson @ncloudioj anyone know who would be good to dig into this to file a separate issue?

Here's a link to the passing build in case we close this PR: https://travis-ci.org/mozilla/activity-stream/builds/160308971

23.38s$ npm install
[email protected] /home/travis/build/mozilla/activity-stream
├─┬ [email protected] 

[k88hudson]

@rlr actually removed history from the code base in a previous commit. @rlr can you do a follow-up to remove this from package.json?