mocha-cloud

Hi there! This change adds the repository property to your package.json file(s). Having this available provides a number of benefits to security tooling. For example, it allows for greater trust by checking for signed commits, contributors to a release and validating history with the project. It also allows for comparison between the source code and the published artifact in order to detect attacks on authors during the publication process. We validate that we're making a PR against the correct repository by comparing the metadata for the published artifact on npmjs.com against the metadata in the package.json file in the repository. This change is provided by a team at Microsoft -- we're happy to answer any questions you may have. (Members of this team include @s-tuli, @iarna, @v-rr, @v-jiepeng, @v-zhzhou and @v-gjy). If you would prefer that we not make these sorts of PRs to projects you maintain, please just say. If you'd like to learn more about what we're doing here, we've prepared a document talking about both this project and some of our other activities around supply chain security here: microsoft/Secure-Supply-Chain This PR provides repository metadata for the following packages: mocha-cloud

I think this occasionally was cutting off the quit request and causing the instance to timeout instead of shutdown immediately. No idea really, though.

This pull request changes the API significantly. Instead of handling events on the client and saving info into mochaResults, we serialize all the event information and send it to the reporter as JSON. By using it can send circular references fine and also re-construct the prototype chains properly on arrival. The upshot of the API change is that you can use any of the standard mocha reporters. Here is a demo of browser side tests running with the reporter: !Imgur Note that the timing at the end is sadly completely erroneous, but could be fixed if the timing was done in the runner and not in the reporter.