Dominik Ferber f1da865eca refactor(): Make Meteor file metadata available to rules
Rules now get the Meteor root directory passed to them. They can use that information to extract further information about the file being linted based on its path in the project.
2015-10-01 10:14:36 +02:00
2015-09-24 19:03:14 +02:00
2015-09-28 00:10:15 +02:00
2015-09-28 00:10:15 +02:00
2015-09-28 13:36:22 +02:00
2015-09-24 19:03:14 +02:00
2015-09-28 15:48:56 +02:00

ESLint-plugin-Meteor

Maintenance Status NPM version Build Status Dependency Status Coverage Status Code Climate semantic-release Commitizen friendly

Meteor specific linting rules for ESLint

Installation

Install ESLint either locally or globally.

$ npm install eslint

If you installed ESLint globally, you have to install Meteor plugin globally too. Otherwise, install it locally.

$ npm install eslint-plugin-meteor

Configuration

Add plugins section and specify ESLint-plugin-Meteor as a plugin.

{
  "plugins": [
    "meteor"
  ]
}

Finally, enable all of the rules that you would like to use.

{
  "rules": {
    "meteor/no-session": 1,
    "meteor/no-blaze-lifecycle-assignment": 2,
    "meteor/no-blaze-zero-timeout": 2,
    "meteor/audit-argument-checks": 2
  }
}

List of supported rules

To Do

  • Add more rules.

Any rule idea is welcome !

Essential Development Resources

These specs and tools help enormously when developing new rules.

Thanks

This plugin is inspired by eslint-plugin-react.

License

ESLint-plugin-Meteor is licensed under the MIT License.

Description
No description provided
Readme MIT 202 MiB
Languages
JavaScript 91.1%
TypeScript 3.9%
Shell 0.9%
Java 0.7%
Swift 0.7%
Other 2.5%