-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Comparing changes
Open a pull request
base repository: mochajs/mocha
base: v8.2.0
head repository: mochajs/mocha
compare: v8.2.1
- 11 commits
- 22 files changed
- 3 contributors
Commits on Oct 16, 2020
-
fix v8.2.0 release date in CHANGELOG.md [ci skip]
Signed-off-by: Christopher Hiller <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for f23035d - Browse repository at this point
Copy the full SHA f23035dView commit details
Commits on Oct 30, 2020
-
add node.js v15 to build matrix
Signed-off-by: Christopher Hiller <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 0165112 - Browse repository at this point
Copy the full SHA 0165112View commit details -
Change assert module's deprecated methods in testing files (#4435)
* Change deprecated methods in assert library * update getDiffs when node version v10 * skip test in no-diff.spec.js when Node.js 10 * revert diffs.spec.js output changes, skip diffs.spec.js when Node.js 10 * skip diffs.spec.js when Node.js 10
Configuration menu - View commit details
-
Copy full SHA for 7e490aa - Browse repository at this point
Copy the full SHA 7e490aaView commit details
Commits on Nov 2, 2020
-
Configuration menu - View commit details
-
Copy full SHA for fac181b - Browse repository at this point
Copy the full SHA fac181bView commit details -
delegate to Node on non-Mocha unhandled rejections (#4489)
This is not intended as a _fix_ for #4481, since it's possible that Mocha's behavior in v8.2.0 uncovers false positives. In other cases--depending on the use-case--they are not false positives at all, but rather annoyances that depended on the pre-v15 behavior of Node.js to only issue warnings. This PR changes the behavior of Mocha so that it will re-emit unhandled rejections to `process` _if_ they did not generate from Mocha. If the rejection generated from Mocha, then we treat it as an uncaught exception, because Mocha should not be in the business of ignoring its own unhandled rejections. The logic for detecting an "error originating from Mocha" is not exhaustive. Once an unhandled rejection is re-emitted to `process`, Node decides what to do with it based on how it is configured to handle unhandled rejections (strict, warn, quiet, etc.). Added a public method to `errors` module; `isMochaError()` Ref: #4481 Signed-off-by: Christopher Hiller <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for c3ced39 - Browse repository at this point
Copy the full SHA c3ced39View commit details -
update deps for some vuln which is not applicable to mocha
Signed-off-by: Christopher Hiller <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 8318dff - Browse repository at this point
Copy the full SHA 8318dffView commit details -
Signed-off-by: Christopher Hiller <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 5c004a9 - Browse repository at this point
Copy the full SHA 5c004a9View commit details -
properly dispose Mocha instance in watch mode; closes #4495
Signed-off-by: Christopher Hiller <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 27cae39 - Browse repository at this point
Copy the full SHA 27cae39View commit details -
ensure eslint runs properly on PRs
Signed-off-by: Christopher Hiller <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for d2e0e83 - Browse repository at this point
Copy the full SHA d2e0e83View commit details -
Signed-off-by: Christopher Hiller <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for bddc079 - Browse repository at this point
Copy the full SHA bddc079View commit details -
Configuration menu - View commit details
-
Copy full SHA for 185cada - Browse repository at this point
Copy the full SHA 185cadaView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v8.2.0...v8.2.1