npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

alarm-reporter

v0.1.1

Published

The reporter for mocha, supports send alarm message when current mocha test run failed

Downloads

6

Readme

alarm-reporter

build status GitHub license node version

NPM

中文

The reporter for mocha, supports send alarm message when current mocha test run failed, it's usageful for continuous integration.

Install

yarn add alarm-reporter --dev

Usage

Set the parameters of --reporter and --reporter-options to mocha in your package.json file, this is an example as follows:

"scripts": {
    "test": "mocha path_for_test_files --timeout 99999 --reporter node_modules/alarm-reporter --reporter-options 'name=project-name,alarm=the_package_name_of_your_alarm_class'"
},

The alarm parameter of repoter-options is a Class, which should have the function of sendSync:

class YourAlarm {
    /**
     * @param {object} reporterOption The parameters from the cli parameter --reporter-options
     */
    constructor(reporterOption) {
    }
    /**
     * @param {string} msg The msg you wanna send to team members
     * @returns {Error?}
     */
    sendSync(msg) {
    }
}

Notice that , the function name ends with Sync, you have to write synchronized code in it. This will been called in the listener of end of mocha, the listener doesn't support asynchronous operations, it will exit when all test run finished, doesn't wait for any asynchronous code, such as operation of doing HTTP requests to your notify center.

You can write your http request code in a single js file, and then use spawnSync to make the request run in synchronized mode.

// util.js
const { spawnSync } = require('child_process');
/**
 * 
 * @param {Object} option
 * @param {String} option.msg The failed msg.
 */
exports.sendSync = function (option) {
    return spawnSync('node', ['sender.js'], {
        env: {
            ...process.env,
            msg: option.msg
        },
        cwd: __dirname,
    });
};
// sender.js

const {msg} = process.env;

// run sendin msg code...

License

MIT