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

dk-eslint-config

v3.4.10

Published

Enterprise-quality ESLint config with TypeScript support

Downloads

226

Readme

Enterprise-quality ESLint config with TypeScript support

npm license

[!WARNING]
It's fine if you use this library from NPM package with a static versioning in case you want it for some pet-project or to test it's capabilities.

But for production use it's strongly recommended to create a fork, because I do not write Changelogs and may break / add some functionality without notice.

Use as is or as an inspiration for your projects.

Includes

  • perfectly configured rules for JavaScript files with React
  • perfectly configured rules for TypeScript files
  • auto-formatting with Prettier integrated in ESLint (runs by eslint --fix)
  • StyleLint rules for *.scss files

Core concepts

  • Syntax with async | generator | await | yield is restricted, use // eslint-ignore if you need this
  • Max depth of blocks is 4, simplify your code by using function composition
  • React is configured for using Class Components, so no long functions with mix of state, side-effects, lifecycle, markup are allowed
  • UNSAFE_componentWillMount is allowed - this is a perfect solution for starting async actions that are executed in SSR
  • Use Type | Props prefixes for types, T prefix for generics - no more confusion whether it is component, class or type
  • Use camelCase for functions, UPPER_CASE for constants and PascalCase for types and classes
  • Use import _ from 'lodash' with babel-plugin-lodash instead of import ... from lodash/.... No more get(), merge() without namespace
  • Use dot object notation like object.param instead of object['param']
  • No forgotten console statements
  • Auto-sort imports
  • Everything can be reconfigured in your own config

And many more best-practices. Recommended for use in scalable enterprise applications.

Usage

  1. Add dk-eslint-config to package.json
  2. Create .eslintrc.js with content:
const { getEslintConfig } = require('dk-eslint-config');

// When you need TypeScript
// const eslintConfig = getEslintConfig({ tsConfigPath: path.resolve(__dirname, './tsconfig.json'), react: true });

const eslintConfig = getEslintConfig({});

module.exports = eslintConfig;
  1. Create .stylelintrc.js with content:
const { stylelintConfig } = require('dk-eslint-config');

module.exports = stylelintConfig;
  1. Create .editorconfig with content:
[*]
max_line_length = 100
indent_style = space
indent_size = 2
  1. Create .formatignore with content (maybe you need other folders like build or dist):
node_modules
.yarn
cache
.cache
.vscode
  1. Add scripts to package.json (example for formatting only pointed files but analyze all files):
{
  "scripts": {
    "analyze:js": "eslint --ignore-path .formatignore --ext \".js,.ts,.tsx\" ./",
    "analyze:style": "stylelint --ignore-path .formatignore \"**/*.scss\"",
    "format:js": "eslint --ignore-path .formatignore --ext \".js,.ts,.tsx\" --fix",
    "format:style": "stylelint --ignore-path .formatignore --fix"
  }
}

Attach StyleLint and ESLint to your IDE, don't forget to enable auto-formatting on save.

It's recommended to add pre-commit hooks. For examples look through this repository. Example of usage:

  1. Add husky (4.3.8 is cross-platform, higher versions are buggy) and lint-staged to devDependencies
  2. Create lint-staged.config.js with content:
const { lintStagedConfig } = require('dk-eslint-config');

module.exports = lintStagedConfig;
  1. Add husky section to package.json:
{
  "husky": {
    "hooks": {
      "pre-commit": "set -e&&lint-staged"
    }
  }
}

Handling imports order

Sometimes you need to define custom groups for imports sorting. Here is an example of .eslintrc.js

const fs = require('fs');
const path = require('path');

const { getEslintConfig } = require('dk-eslint-config');

const eslintConfig = getEslintConfig({
  react: true,
  tsConfigPath: path.resolve(__dirname, './tsconfig.json'),
});

/**
 * eslint-plugin-import considers all imports like './env.ts' | './paths.ts' as external
 *
 * but for better readability we need to treat them as internal to separate from
 * imports from 'node_modules' folder
 *
 */

const pathGroups = [
  { pattern: 'env', group: 'internal' },
  { pattern: 'paths', group: 'internal' },
];

/**
 * let's treat all files in ./src as internal (for ex. Webpack is configured with this alias)
 *
 */

fs.readdirSync(path.resolve(__dirname, 'src')).forEach((fileName) => {
  const fileNameNoExt = path.parse(fileName).name;

  pathGroups.push({ pattern: fileNameNoExt, group: 'internal' });
  pathGroups.push({ pattern: `${fileNameNoExt}/**`, group: 'internal' });
});

eslintConfig.rules = {
  'import/order': [
    'error',
    {
      'newlines-between': 'always',
      groups: ['builtin', 'external', 'internal', 'unknown', 'parent', 'sibling', 'index'],
      pathGroups,
      pathGroupsExcludedImportTypes: ['internal'],
    },
  ],
};

module.exports = eslintConfig;