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

mocha-for-jetbrains

v1.0.1

Published

mocha replacement that allows to specify patterns for test files

Downloads

504

Readme

mocha-for-jetbrains

The module is a replacement for mocha runner that allows to specify patterns and directories in the Jetbrains (webstorm, pycharms, intellij, ...) Mocha Debug Configuration.

This is a fix for Jetbrains issue WEB-10067 Run a single Mocha unit-test

How to use it

Install this package next to mocha and use /path/to/node_modules/mocha-for-jetbrains instead of /path/to/node_modules/mocha into the Mocha Package field.

Just add the patterns and directories you wan to test as first arguments in the Extra Mocha Options options.

If you add Extra Mocha Options into the Extra Mocha Options field

**/*.node.test.js foo/special-test.js

It will run the specified tests instead of all tests with the specified patterns.

If you want to specify some additional options, you have to do it after the patterns:

**/*.node.test.js foo/special-test.js --slow 500   

This module essentially takes all arguments before the first option that starts with a - and adds them to the end of the command line. If no files are given, then ist uses the directory specified in the Test Directory field.

Installation

Install the module next to the mocha installation. So, if you have installed

npm install -g mocha

then you have to install this module globally:

npm install -g mocha-for-jetbrains

If you have installed mocha locally, then you have to install this module locally too:

npm install mocha --save-dev

then you have to install it locally too:

npm install mocha-for-jetbrains --save-dev

How to specify another mocha runtime

If you want to use another mocha instance instead of the one next to this module you can specify the mocha to use with the --mocha in the Extra Mocha Options field. It uses the same convention that is used in the Mocha Pakage field in the Mocha Debug Configuration dialog.