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-no-restricted

v0.0.8

Published

An eslint utility for quickly and easily creating no-restricted-syntax rules.

Downloads

245,161

Readme

eslint-no-restricted

An eslint utility for quickly and easily creating no-restricted-syntax rules.

This utility is a more powerful alternative to the core rules no-restricted-syntax, no-restricted-globals, and no-restricted-properties.

There are two major features you get with this utility over the core rules:

(1) This utility creates one rule per selector/global/property, rather than having one rule for everything. Having multiple rules is useful for many reasons! It allows you to:

  • Configure each selector/global/property with a different severity
  • Easily enable or disable specific selector/global/property on specific files/folders
  • Ensure that one disable comment does not suppress multiple selector/global/property

(2) This utility allows you to create messages with placeholders. This is powerful because it allows you to provide more targeted, less generic messages to provide a better and more understandable DevX.

Installation

npm i eslint-no-restricted

Example Usage

For brevity following example shows usage of the no-restricted-syntax utility - but the same API is available for the globals and properties variants too.

// eslint.config.mjs

import createNoRestrictedSyntax from 'eslint-no-restricted/syntax';

const noRestrictedSyntax = createNoRestrictedSyntax(
  // define a single selector with a message
  {
    message: 'errors on identifiers named foo',
    name: 'ban-the-name-foo',
    selector: 'Identifier[name = "foo"]',
  },

  // define multiple selectors with the same message
  {
    message: 'errors on the string "bar"',
    name: 'do-not-allow-the-string-bar',
    selector: [
      'Literal[value = "bar"]',
      'TemplateLiteral[quasis.length = 1] > TemplateElement[value.cooked = "bar"]',
    ],
  },

  // define one or more selectors with a placeholder derived from the matched node
  {
    message: 'this message has a placeholder ->{{placeholder}}<-',
    messageData: (node, sourceCode) => {
      if (node.parent?.type === 'VariableDeclarator') {
        return {
          placeholder: sourceCode.getText(node.parent.id),
        };
      }
      return {
        placeholder: 'wtf',
      };
    },
    name: 'disallow-the-number-1',
    selector: 'Literal[value = 1]',
  },
);

export default [
  // turn on all of the rules using the auto-generated configuration
  noRestrictedSyntax.configs.recommended,

  // you can also manually configure the rules
  {
    files: ['**/some-glob/*.js'],
    plugins: {
      nrs: noRestrictedSyntax,
    },
    rules: {
      'nrs/disallow-the-number-1': 'off',
    },
  },
];