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 browserify.
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.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Coverage remained the same at 90.845% when pulling f90786cf27c82fe93ec73c4932cce84447b4eb4e on greenkeeper-browserify-14.2.0 into 215bfb9d9354a8e5851d87120b2e66fd2d4e37ec on master.
Hello lovely humans,
browserify just published its new version 14.2.0.
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 browserify. 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 :sparkles:
You rock!
:palm_tree:
The new version differs by 36 commits .
18e1d65
14.2.0
0e1a7a0
add cli support for --transform-key to support mode's like production/staging/etc..
a5aa660
Merge pull request #1701 from wogsland/doc-fix
ae281bc
Fixed documentation formatting that was bugging me
fe8c57b
async test for node 7
06a47d1
14.1.0
67ea8b1
Merge branch 'patch-1' of https://github.com/natevw/node-browserify
691239d
14.0.0
60cd894
changelog: 14.0.0
d7ea3dd
Merge pull request #1678 from substack/buffer-5
4f5d93b
test: pass Uint8Array into vm context for buffer v5
ae33350
Update 'buffer' to v5.x
ea6c299
Write to temp outfile until success, fixes #899
6efcd65
13.3.0
cbc20ac
use carat on assert package
There are 36 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.