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 debug.
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.
23af483Merge remote-tracking branch 'upstream/master' into replace-babel-with-browserify
3e1a15dfix: merged again, because it didn't take. Guess I did it wrong?
67182fdfix: Whoops, didn't merge the tests properly. Resolved.
2a01c6cMerged from upstream/master. I left the dist/debug in place because my hook now updates it automatically, but I removed the babelrc file since we don't need it anymore.
6e934e9Fix for #381. Moved .babelrc into test folder, where it is used and which is not built with the module. (#383)
Hello lovely humans,
debug just published its new version 2.5.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 debug. 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 40 commits .
355e327release 2.5.0d85c0c6build perf, fix for bowerfile, fix for webworkerdc043cfMerge pull request #378 from yamikuronue/replace-babel-with-browserifyf512cf2Merge remote-tracking branch 'upstream/master' into replace-babel-with-browserifyf098331Merge pull request #388 from ForsakenHarmony/patch-1a16cf42Merge pull request #387 from kribblo/patch-178e31a8Update browser.js408ae94Use typeof window.process !== 'undefined'f484cfefix merge errors23af483Merge remote-tracking branch 'upstream/master' into replace-babel-with-browserify3e1a15dfix: merged again, because it didn't take. Guess I did it wrong?67182fdfix: Whoops, didn't merge the tests properly. Resolved.2a01c6cMerged from upstream/master. I left the dist/debug in place because my hook now updates it automatically, but I removed the babelrc file since we don't need it anymore.6e934e9Fix for #381. Moved .babelrc into test folder, where it is used and which is not built with the module. (#383)6a8d525chore: add coverallsThere are 40 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade