Eslint-config-mskcc-dev NPM

eslint-config-mskcc-dev

GitHub tag (latest SemVer) GitHub issues GitHub closed issues GitHub pull requests GitHub closed pull requests

DEVELOPMENT REPOSITORY

This package provides MSKCC base eslint configurations to keep consistency with all our teams. Use this as the base to your project. These configurations will be continuously updated.

Usage

// create `.eslintrc` file in your project's root folder and add

{
  "extends": "mskcc"
}

Current configurations:

Type	"extends" path	Description
ES6+	`mskcc`	ESM config
React	`mskcc/react`	ReactJS specific config
React with TypeScript	`mskcc/react-typescript`	ReactJS, TypeScript, uses `eslint-config-prettier`, `eslint-plugin-prettier`, `eslint-plugin-react`, `eslint-plugin-react-hooks`, `@types/eslint`, `@typescript-eslint/eslint-plugin`, `@typescript-eslint/parser`
Vue	`mskcc/vue`	Vue 2, uses `eslint-plugin-vue` , `vue-eslint-parser`

Contribution

Request configurations

We are developing based around consistency throughout all engineers. If there are settings that you feel would benefit the community as a whole, please add your request using the link above.

@rushstack/eslint-patch

Making external plugins a dependency so the user don't have to manually install the plugins.

https://www.npmjs.com/package/@rushstack/eslint-patch

How to use it

Add a require() call to the to top of the .eslintrc.js file for each project that depends on your shared ESLint config, for example:

.eslintrc.js

require("@rushstack/eslint-patch/modern-module-resolution");

// Add your "extends" boilerplate here, for example:
module.exports = {
  extends: ['@your-company/eslint-config'],
  parserOptions: { tsconfigRootDir: __dirname }
};