Update browserify to the latest version 🚀

[greenkeeper]

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 16.2.0 of browserify was just published.

Dependency	browserify
Current Version	16.1.1
Type	devDependency

The version 16.2.0 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of browserify.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

---

Release Notes

v16.2.0

update the browser versions of vm-browserify and string_decoder.

string_decoder updates to the Node 8+ API.
vm-browserify replaces an unlicensed dependency by an MIT one.

#1829

Commits

The new version differs by 5 commits.

• 00cc377 16.2.0
• 7005b6e Merge pull request #1829 from browserify/deps
• e333b14 Merge pull request #1827 from browserify/fix-cert
• 03ffac9 ci: Disable certificate check for very old npm
• 9345e21 Update string_decoder and vm builtin modules

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 🌴