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

eslint-plugin-always

v2.2.0

Published

ESLint plugin that always reports with configurable message

Downloads

1,780

Readme

NPM version Downloads star this repo fork this repo CI

eslint-plugin-always

ESLint plugin that always reports with a configurable message.

Simply reports ALWAYS!

There is a reason why we want to do so! See Why?

Installation

$ yarn add eslint-plugin-always --dev

Usage

Add the plugin to your ESLint configuration:

{
  "plugins": [
    "always"
  ]
}

And then add the following rule:

{
  "rules": {
    "always/always": ["error", {
      "message": "Hello World"
    }]
  }
}

Why?

I need to notice the team members that the new folder must contain a ESLint configuration.

Notice

I will simply show you the use case which is the reason why I created this plugin.

There is a cartridges/ folder in the project. This folder contains multiple packages which may need a different ESLint configuration.

The surrounding application uses another ESLint configuration. But this configuration isn't applicable for the packages in the cartridges/ folder.

├── cartridges
│   ├── app_foo
│   │   ├── .eslintrc.json
│   ├── int_foo
│   │   ├── .eslintrc.json
│   ├── int_bar
│   │   ├── .eslintrc.json
│   ├── int_new <-- DETECT WHY THIS FOLDER DOESN'T HAVE A LINT CONFIGURATION
│   ├── bc_foo
│   │   ├── .eslintrc.json
│   ├── .eslintrc.json <-- THE FILE THAT ENABLES THIS RULE AND CONTAINING root: true
├── packages.json <-- CONTAINING THE SURROUNDING LINT CONFIGURATION

For a new package cartidges/int_new a valid ESLint configuration must be added.

cartridges/.eslintrc.json resets the ESLint configuration and adds this rule.

{
  "root": true,
  "plugins": [
    "always"
  ],
  "rules": {
    "always/always": ["error", {
      "message": "No ESLint config found. Please add one or ignore the cartridge."
    }]
  }
}

So all files in this folder structure won't check any ESLint rules. The subfolders must contain ESLint configurations which can differ between each subfolder.

For the case that someone adds a subfolder and forgets the ESLint configuration this rule was created. So every file within the subfolder will report an error

No ESLint config found. Please add one or ignore the cartridge.

License

MIT © 2023 Jens Simon