eslint-plugin-import - ESLint plugin with rules that help validate proper imports.

  •        50

This plugin intends to support linting of ES2015+ (ES6+) import/export syntax, and prevent issues with misspelling of file paths and import names. All the goodness that the ES2015+ static module syntax intends to provide, marked up in your editor. IF YOU ARE USING THIS WITH SUBLIME: see the bottom section for important info.

https://github.com/benmosher/eslint-plugin-import

Dependencies:

contains-path : ^0.1.0
debug : ^2.6.8
doctrine : 1.5.0
eslint-import-resolver-node : ^0.3.1
eslint-module-utils : ^2.2.0
has : ^1.0.1
lodash : ^4.17.4
minimatch : ^3.0.3
read-pkg-up : ^2.0.0
resolve : ^1.6.0

Tags
Implementation
License
Platform

   




Related Projects

eslint-plugin-node - Additional ESLint's rules for Node.js

  •    Javascript

Note: It recommends a use of the "engines" field of package.json. The "engines" field is used by node/no-unsupported-features/* rules. eslint-plugin-node follows semantic versioning and ESLint's Semantic Versioning Policy.

eslint-plugin-babel - An ESlint rule plugin companion to babel-eslint

  •    Javascript

An eslint plugin companion to babel-eslint. babel-eslint does a great job at adapting eslint for use with Babel, but it can't change the built in rules to support experimental features. eslint-plugin-babel re-implements problematic rules so they do not give false positives or negatives.Finally enable all the rules you would like to use (remember to disable the original ones as well!).

eslint-plugin-react-native - React Native plugin for ESLint

  •    Javascript

React Native specific linting rules for ESLint. This repository is structured like (and contains code from) the excellent eslint-plugin-react. Install ESLint either locally or globally.

eslint-plugin-prettier - ESLint plugin for prettier formatting

  •    Javascript

Runs Prettier as an ESLint rule and reports differences as individual ESLint issues. ./node_modules/.bin/eslint --format codeframe pkg/commons-atom/ActiveEditorRegistry.js (code from nuclide).

eslint-plugin-angular - ESLint plugin for AngularJS applications

  •    Javascript

ESLint rules for your angular project with checks for best-practices, conventions or potential errors.This repository will give access to new rules for the ESLint tool. You should use it only if you are developing an AngularJS application.


eslint-plugin-react - React specific linting rules for ESLint

  •    Javascript

Install ESLint either locally or globally. If you installed ESLint globally, you have to install React plugin globally too. Otherwise, install it locally.

eslint-plugin-promise - Enforce best practices for JavaScript promises

  •    Javascript

Enforce best practices for JavaScript promises. Note: If you installed ESLint globally (using the -g flag) then you must also install eslint-plugin-promise globally.

typescript-eslint - :sparkles: Monorepo for all the tooling which enables ESLint to support TypeScript

  •    TypeScript

The following sections will give you an overview of what this project is, why it exists and how it works at a high level. It is very important that you are familiar with these concepts before reporting issues, so please read them and let us know if you have any feedback.

eslint-plugin-jsx-a11y - Static AST checker for a11y rules on JSX elements.

  •    Javascript

Static AST checker for accessibility rules on JSX elements. Ryan Florence built out this awesome runtime-analysis tool called react-a11y. It is super useful. However, since you're probably already using linting in your project, this plugin comes for free and closer to the actual development process. Pairing this plugin with an editor lint plugin, you can bake accessibility standards into your application in real-time.

linter-eslint - ESLint plugin for Atom Linter

  •    Javascript

This linter plugin for Linter provides an interface to eslint. It will be used with files that have the "JavaScript" syntax. linter-eslint will look for a version of eslint local to your project and use it if it's available. If none is found it will fall back to the version it ships with.

eslint-plugin-immutable - ESLint plugin to disable all mutation in JavaScript.

  •    Javascript

This is an ESLint plugin to disable all mutation in JavaScript. Think this is a bit too restrictive? Well if you're using Redux and React, there isn't much reason for your code to be mutating anything. Redux maintains a mutable pointer to your immutable application state, and React manages your DOM state. Your components should be stateless functions, translating data into Virtual DOM objects whenever Redux emits a new state. These ESLint rules explicitly prohibit mutation, effectively forcing you to write code very similar to Elm in React. There's no reason to use let in a Redux/React application, because all your state is managed by either Redux or React. Use const instead, and avoid state bugs altogether.

eslint-plugin-flowtype-errors - Run Flow as an ESLint plugin

  •    Javascript

This guide assumes that you have installed eslint, babel, babel-plugin-transform-flow-strip-types and configured flow. Check out the from-scratch guide for the full guide on getting started. Add this line to the 'rules' section of your .eslintrc to report flow errors.

eslint-plugin-flowtype - Flow type linting rules for ESLint.

  •    Javascript

Flow type linting rules for ESLint. This plugin exports a recommended configuration that enforces Flow type good practices.

SublimeLinter-eslint - This linter plugin for SublimeLinter provides an interface to ESLint

  •    Python

This linter plugin for SublimeLinter provides an interface to ESLint. It will be used with files that have the "javascript" syntax. SublimeLinter 3 must be installed in order to use this plugin.

eslint-config-cleanjs - An eslint config which reduces JS to a pure functional language

  •    Javascript

This is an ESLint configuration which aims to restrict you to a subset of JavaScript which would be as close to an idealised pure functional language as possible. The idea is to see if it's possible to banish all the Bad Parts (well, except for the single numeric type being IEEE 754 floating point) and leave a language without the design flaws which have plagued JS from the start, and which aren't easy to design out of the language without becoming a subset of itself. Please note that this rule set is meant for use only with ES6 or higher (and the ES7 object rest spread proposal helps a lot).