Update browserify to the latest version 馃殌 - #40
Open
greenkeeper[bot] wants to merge 1 commit into
Open
greenkeeper[bot] wants to merge 1 commit into
greenkeeper[bot] wants to merge 1 commit into
Conversation
Contributor
Author
Version 16.2.2 just got published.Update to this version instead 馃殌 Release Notesv16.2.2Remove some extraneous files from the published package. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version 16.2.1 of browserify was just published.
browserifyThe version 16.2.1 is not covered by your current version range.
If you don鈥檛 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鈥檛 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
--externalpaths on Windows. (@Shingyx)#1704
Fix tests to work on Windows, and add Appveyor CI for Windows testing.
#1819
Commits
The new version differs by 36 commits.
36d7c9a16.2.1e34599aMerge pull request #1819 from goto-bus-stop/appveyor8e7cb87Skip flaky test on Windows w old Node3703154Disable invalid json chars test in node 10e39d609Skip failing test on old Node on Windowsc428f0cFix external relative paths on Windowsc5120b7Fix tests on Windows.2d896a9Try adding appveyor00cc37716.2.07005b6eMerge pull request #1829 from browserify/depse333b14Merge pull request #1827 from browserify/fix-cert03ffac9ci: Disable certificate check for very old npm9345e21Update string_decoder and vm builtin modules25c71db16.1.1fa00040Merge pull request #1815 from browserify/ignore-perf-hooksThere are 36 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don鈥檛 help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 馃尨