The version 16.2.1 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 Notesv16.2.1
Fix relative --external paths on Windows. (@Shingyx)
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Coverage remained the same at 93.382% when pulling 03f00d327046cf629212fb7b2e324ede1eb4216b on greenkeeper/browserify-16.2.1 into c5af0448972ddbcbd4cae7205532cdcd8aae858c on master.
Version 16.2.1 of browserify was just published.
browserify
The version 16.2.1 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.1Fix relative
--external
paths on Windows. (@Shingyx)#1704
Fix tests to work on Windows, and add Appveyor CI for Windows testing.
#1819
Commits
The new version differs by 8 commits.
36d7c9a
16.2.1
e34599a
Merge pull request #1819 from goto-bus-stop/appveyor
8e7cb87
Skip flaky test on Windows w old Node
3703154
Disable invalid json chars test in node 10
e39d609
Skip failing test on old Node on Windows
c428f0c
Fix external relative paths on Windows
c5120b7
Fix tests on Windows.
2d896a9
Try adding appveyor
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: