Update dependency mocha to v5 - autoclosed #105
Closed
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.
This PR contains the following updates:
^2.4.5
->^5.0.0
By merging this PR, the below issues will be automatically resolved and closed:
Release Notes
mochajs/mocha
v5.0.3
Compare Source
This patch features a fix to address a potential "low severity" ReDoS vulnerability in the diff package (a dependency of Mocha).
🔒 Security Fixes
diff
to v3.5.0 (@anishkny)🔩 Other
generateDiff()
inBase
reporter (@harrysarson)v5.0.2
Compare Source
This release fixes a class of tests which report as false positives. Certain tests will now break, though they would have previously been reported as passing. Details below. Sorry for the inconvenience!
🐛 Fixes
#3226: Do not swallow errors that are thrown asynchronously from passing tests (@boneskull). Example:
```js
it('should actually fail, sorry!', function (done) {
// passing assertion
assert(true === true);
// test complete & is marked as passing
done();
// ...but something evil lurks within
setTimeout(() => {
throw new Error('chaos!');
}, 100);
});
```
Previously to this version, Mocha would have silently swallowed the
chaos!
exception, and you wouldn't know. Well, now you know. Mocha cannot recover from this gracefully, so it will exit with a nonzero code.Maintainers of external reporters: If a test of this class is encountered, the
Runner
instance will emit theend
event twice; you may need to change your reporter to userunner.once('end')
intead ofrunner.on('end')
.#3093: Fix stack trace reformatting problem (@outsideris)
🔩 Other
browser-stdout
to v1.3.1 (@honzajavorek)v5.0.1
Compare Source
...your garden-variety patch release.
Special thanks to Wallaby.js for their continued support! ❤️
🐛 Fixes
--delay
now works with.only()
(@silviom)📖 Documentation
--glob
docs (@outsideris)🔩 Other
v5.0.0
Compare Source
Mocha starts off 2018 right by again dropping support for unmaintained rubbish.
Welcome @vkarpov15 to the team!
💥 Breaking Changes
Practically speaking, only code which consumes (through bundling or otherwise) the userland buffer module should be affected. However, Mocha will no longer test against these browsers, nor apply fixes for them.
🎉 Enhancements
--file
command line argument (documentation) (@hswolff)🐛 Fixes
😎 Developer Experience
📖 Documentation
--no-timeouts
docs (@dfberry)done()
callback docs (@maraisr)README.md
organization (@xxczaki)🔩 Other
v4.1.0
Compare Source
4.1.0 / 2017-12-28
This is mainly a "housekeeping" release.
Welcome @Bamieh and @xxczaki to the team!
🐛: Fixes
progress
reporter now accepts reporter options (@canoztokmak)xit
inbdd
interface now properly returns itsTest
object (@Bamieh)--help
will now help you even if you have amocha.opts
(@Zarel)🎉 Enhancements
--no-diff
flag will completely disable diff output (@CapacitorSet)📖 Documentation
docs/
(@boneskull)🔩 Other
v4.0.1
Compare Source
4.0.1 / 2017-10-05
🐛 Fixes
v4.0.0
Compare Source
4.0.0 / 2017-10-02
You might want to read this before filing a new bug! 😝
💥 Breaking Changes
For more info, please read this article.
Compatibility
Default Behavior
node
from exiting will do so when run in Mocha. Supply the--exit
flag to revert to pre-v4.0.0 behavior (@ScottFreeCode, @boneskull)Reporter Output
stdout:
prefix from browser reporter logs (@skeggse)--forbid-pending
or--forbid-only
is specified (@ScottFreeCode)👎 Deprecations
--compilers
command-line option is now soft-deprecated and will emit a warning onSTDERR
. Read this for more info and workarounds (@ScottFreeCode, @boneskull)🎉 Enhancements
📖 Documentation
README.md
andCONTRIBUTING.md
(@skeggse)🔩 Other
v3.5.3
Compare Source
3.5.3 / 2017-09-11
🐛 Fixes
v3.5.2
Compare Source
3.5.2 / 2017-09-10
🐛 Fixes
v3.5.1
Compare Source
3.5.1 / 2017-09-09
📰 News
🐛 Fixes
xit
export for "require" interface (@solodynamo)🔩 Other
--compilers
coverage (@ScottFreeCode)v3.5.0
Compare Source
v3.5.0 / 2017-07-31
📰 News
🔒 Security Fixes
🎉 Enhancements
--forbid-only
and--forbid-pending
flags. Use these in CI or hooks to ensure tests aren't accidentally being skipped! (@charlierudolph)--napi-modules
flag (@jupp0r)🔩 Other
v3.4.2
Compare Source
3.4.2 / 2017-05-24
🐛 Fixes
🔩 Other
v3.4.1
Compare Source
Fixed a publishing mishap with git's autocrlf settings.
v3.3.0
Compare Source
Thanks to all our contributors, maintainers, sponsors, and users! ❤️
As highlights:
🎉 Enhancements
--inspect-brk
on command-line (@igwejk)🐛 Fixes
🔍 Coverage
🔩 Other
semistandard
directly (@kt3k)v3.2.0
Compare Source
3.2.0 / 2016-11-24
📰 News
Mocha is now a JS Foundation Project!
Mocha is proud to have joined the JS Foundation. For more information, read the announcement.
Contributor License Agreement
Under the foundation, all contributors to Mocha must sign the JS Foundation CLA before their code can be merged. When sending a PR--if you have not already signed the CLA--a friendly bot will ask you to do so.
Mocha remains licensed under the MIT license.
🐛 Bug Fix
--watch
encounters broken symlinks (@villesau)list
reporter (@Aldaviva)🎉 Enhancement
--inspect
flag to CLI help (@ughitsaaron)🔩 Other
README.md
(@boneskull, @ScottFreeCode, @dasilvacontin)Thanks to all our contributors, sponsors and backers! Keep on the lookout for a public roadmap and new contribution guide coming soon.
v3.1.2
Compare Source
3.1.2 / 2016-10-10
🐛 Bug Fix
Error
'sstack
property isn't writable ([@boneskull])v3.1.1
Compare Source
3.1.1 / 2016-10-09
🐛 Bug Fix
done()
was called multiple times when it wasn't (@frankleonrose)🔩 Other
.js
files ([@boneskull])v3.1.0
Compare Source
3.1.0 / 2016-09-27
🎉 Enhancement
--inspect
on command-line (@simov)🐛 Bug Fix
this.skip()
is called (@boneskull)SIGINT
encountered; exit code can no longer rollover at 256 (@Munter)only()
/skip()
in IE7/IE8 (@boneskull)String
constructor (more) (@boneskull)v3.0.2
Compare Source
v3.0.1
Compare Source
v3.0.0
Compare Source