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-line

v0.0.1

Published

Run mocha tests at a given line number

Downloads

746

Readme

mocha-line

Run mocha tests at a given line number.

Why?

Mocha is a solid test runner, but it does not support running tests at a given line number, instead opting for using a --grep matcher. This module aims to augment that behavior by converting a given line number to a --grep pattern.

Installation

yarn global add mocha-line

(Doesn't have to be global, but is easier this way)

Usage

Basic usage:

> mocha-line ./test/controllers/users.spec.js:72

UsersController.index\(\) returns a JSON list of users

Usage with Mocha:

Mocha-line currently returns only the grep pattern, so this must be passed to mocha:

NODE_ENV=test ./node_modules/.bin/mocha ./test/controllers/users.spec.js --grep "$( mocha-line ./test/controllers/users.spec.js:72 )"

This is a bit verbose and repetitive (something on the roadmap below), so it's useful to map this to a script, like below in VSCode:

Usage in VSCode:

To use within VSCode, set up your tasks.json file to include the following task:

{
  // See https://go.microsoft.com/fwlink/?LinkId=733558
  // for the documentation about the tasks.json format
  "version": "2.0.0",
  "tasks": [
    {
      "label": "Run Test at Cursor (Mocha)",
      "type": "shell",
      "command": "NODE_ENV=test ./node_modules/.bin/mocha ${relativeFile} --grep \"$( mocha-line ${file}:${lineNumber} )\"",
      "group": "test",
      "presentation": {
          "echo": true,
          "reveal": "always",
          "focus": false,
          "panel": "new"
      }
    }
  ]
}

Roadmap

  • [x] Convert mocha test line numbers to basic grep pattern
  • [ ] Improve grep pattern by including all nested describes
  • [ ] Spawn a mocha process directly from mocha-line (with mocha opts)