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-config-ahmed

v1.2.0

Published

Ahmed's Preferred Strict ESlint Configration

Downloads

7

Readme

eslint-config-ahmed

Ahmed's Prefered Strict ESLint Configuration

Plugins included:

Note: you need to install those plugins by yourself.

Installation

To installed it as dependency into your project, run:

$ npm install --save-dev eslint-config-ahmed

Usage

To use this config,

  1. Create a .eslintrc.js file in the root of your project's directory. (make sure to use js with your your .eslintrc file)
  2. Then merge in the baseConfig() rules in your .eslintrc.js file, for example:
// your eslintrc.js file
const baseConfig = require("eslint-config-ahmed");

module.exports = {
  rules: Object.assign({}, baseConfig(), {
    // Here you can add your own rules to overide intial rules.
  }),
};
  1. You can add scripts to your package.json to lint and/or fix:
"scripts": {
  "test:lint": "eslint .",
  "test:lint-fix": "eslint --fix .",
  "test": "npm run test:lint"
}

Settings

You can easily enable any rules for the plugins you use like react, import, and jest, do it like so:

// your eslintrc.js file
const baseConfig = require("eslint-config-ahmed");

module.exports = {
  rules: Object.assign({}, baseConfig({ import: true, react: true }), {
    // Here you can add your own rules to overide intial rules.
  }),
};

Note: you need to install plugins that mentioned above by yourself.

Here is a full example:

const baseConfig = require("eslint-config-ahmed");

module.exports = {
  root: true,
  plugins: [
    "import",
    "react",
    "react-hooks",
    "prettier", // Recommended Prettier plugin
    "css-modules", // if you are using css modules in your project
  ],
  // For parser options, you can use the default like below, or use `parser: "babel-eslint"`
  parserOptions: {
    sourceType: "module",
    ecmaFeatures: {
      jsx: true,
    },
  },
  env: {
    es6: true,
    // node: true, // If you use it with Node then enable this.
  },
  rules: Object.assign(
    {},
    baseConfig({ flow: true, import: true, jest: true, react: true }),
    // Here you can add your own rules to overide intial rules:
    {
      "prettier/prettier": "error",
      "css-modules/no-undef-class": "error",
    }
  ),
  // Override Configure for Specific files
  overrides: [
    {
      // Jest.
      files: ["*.test.js"],
      env: { jest: true },
      // As you seen here we can enable Jest rules only for test
      // using `jest: true` and turn off `builtin` rules
      rules: baseConfig({ builtin: false, jest: true }),
    },
    {
      // If you are working with Storybook
      files: ["stories.js"],
      globals: {
        module: false,
      },
    },
    {
      // Node.js code.
      files: ["server/**/*.js"],
      env: { node: true },
      rules: {
        "import/order": ["error", { "newlines-between": "always" }],
      },
    },
  ],
  // Here you can add Shared Settings, for example
  settings: {
    react: {
      version: "detect",
    },
  },
};