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

@welldone-software/eslint-plugin

v0.5.2

Published

Custom eslint rules used in various Welldone-Software's projects

Downloads

121

Readme

@welldone-software/eslint-plugin

Prevent to use anything except import/export

Installation

You'll first need to install ESLint:

$ npm i eslint --save-dev

Next, install @welldone-software/eslint-plugin:

$ npm install @welldone-software/eslint-plugin --save-dev

Note: If you installed ESLint globally (using the -g flag) then you must also install @welldone-software/eslint-plugin globally.

Usage

Add @welldone-software to the plugins section of your .eslintrc configuration file. You can omit the eslint-plugin- prefix:

{
  "plugins": ["@welldone-software"]
}

Then configure the rules you want to use under the rules section.

{
  "rules": {
    "@welldone-software/modules-engagement": "error",
  }
}

Plugins

Rules of Modules Engagement

(@welldone-software/modules-engagement)

This rule enforces Welldone's standard file structure. More details about the rule can be found here.

config:

These are the possible configs and their defaults for the rule:

{
  "rules": {
    "@welldone-software/modules-engagement": ["error", {
      // provide a glob to only lint certain paths. F.E:
      //   glob": "/packages/!(common-package)/**/!(*.stories|*.test).js"
      "glob": null, 
      
      // path of modules under package.json's
      "modulesPath": "/src",
      
      // Levels to enforce imports between modules
      "modulesLevels": {'common': 1, 'shared': 1, 'app': 3},
      
      // Default level for other modules
      "middleModulesLevel": 2,
      
      // Allow importing from inner paths in modules. F.E:
      // "moduleInnerPaths": ['/components']
      "moduleInnerPaths": [],
      
      // Array of modules that can be used not only from their root path
      "ignoreInnerPathsForModules": ['common', 'shared']
    }],
  }
}

Supported Rules

  • Fill in provided rules here