This version is covered by your current version range and after updating it in your project the build kept failing.
It looks like your project, in its current form, is malfunctioning and this update didn’t really change that. I don’t want to leave you in the dark about updates though. I recommend you get your project passing and then check the impact of this update again.
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.
Coverage remained the same at 90.845% when pulling 1ebfc51b3def0257da31050961981f503fe850ba on greenkeeper-browserify-13.1.1 into 215bfb9d9354a8e5851d87120b2e66fd2d4e37ec on master.
Coverage remained the same at 90.845% when pulling 1ebfc51b3def0257da31050961981f503fe850ba on greenkeeper-browserify-13.1.1 into 215bfb9d9354a8e5851d87120b2e66fd2d4e37ec on master.
Coverage remained the same at 90.845% when pulling 1ebfc51b3def0257da31050961981f503fe850ba on greenkeeper-browserify-13.1.1 into 215bfb9d9354a8e5851d87120b2e66fd2d4e37ec on master.
Coverage remained the same at 90.845% when pulling 1ebfc51b3def0257da31050961981f503fe850ba on greenkeeper-browserify-13.1.1 into 215bfb9d9354a8e5851d87120b2e66fd2d4e37ec on master.
Coverage remained the same at 90.845% when pulling 1ebfc51b3def0257da31050961981f503fe850ba on greenkeeper-browserify-13.1.1 into 215bfb9d9354a8e5851d87120b2e66fd2d4e37ec on master.
Coverage remained the same at 90.845% when pulling 1ebfc51b3def0257da31050961981f503fe850ba on greenkeeper-browserify-13.1.1 into 215bfb9d9354a8e5851d87120b2e66fd2d4e37ec on master.
Coverage remained the same at 90.845% when pulling 1ebfc51b3def0257da31050961981f503fe850ba on greenkeeper-browserify-13.1.1 into 215bfb9d9354a8e5851d87120b2e66fd2d4e37ec on master.
Hello lovely humans,
browserify just published its new version 13.1.1.
This version is covered by your current version range and after updating it in your project the build kept failing.
It looks like your project, in its current form, is malfunctioning and this update didn’t really change that. I don’t want to leave you in the dark about updates though. I recommend you get your project passing and then check the impact of this update again.
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 13 commits .
c3a4424
13.1.1
10b93d8
use cached-path-relative fixes from https://github.com/substack/node-browserify/pull/1544
8f5ebbf
13.1.0
7fbaee2
Add option to turn off deduping
071642a
Update changelog, credit contributor
1491be4
13.0.1
50b4e8d
Merge pull request #1555 from jmm/use-native-isarray
14e92f9
Eliminate isarray dep
0106bd3
Use native Array.isArray
8f7adc9
Merge pull request #1480 from MellowMelon/doc-ctor-require
f556693
Wrap an offensively long line
58e8c5c
Document some missing cli and constructor options
b2374ce
fix typo
See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade