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

@funboxteam/eslint-plugin-no-only-tests

v5.0.0

Published

Disallow the use of describe.only() and it.only()

Downloads

3,425

Readme

@funboxteam/eslint-plugin-no-only-tests

npm

Disallow the use of describe.only() and it.only().

По-русски

Rationale

When developers fix tests they may make the process easier by filtering tests using method only on it & describe.

However, such filters should not be in the repo when the project is running on CI. So, we add this rule to our ESLint config to check the existence of only in the tests files. And we run linter using precommit-hook, which make it possible to prevent committing when only does exist in the code.

Installation

You'll first need to install ESLint:

$ npm i eslint --save-dev

Next, install the plugin:

$ npm install @funboxteam/eslint-plugin-no-only-tests --save-dev

Usage

Add @funboxteam/eslint-plugin-no-only-tests to the plugins section of your .eslintrc configuration file. You can omit the eslint-plugin- prefix:

{
  "plugins": [
    "@funboxteam/no-only-tests"
  ]
}

Then configure the rule under the rules section.

{
  "rules": {
    "@funboxteam/no-only-tests/no-only": 2
  }
}

Sponsored by FunBox