Meteor specific linting rules for ESLint

Usage no npm install needed!

<script type="module">
  import eslintPluginMeteor from '';



Meteor specific linting rules for ESLint

Build Status Coverage Status Dependency Status

Join the chat at Maintenance Status semantic-release Commitizen friendly

License NPM version NPM downloads


This gif shows integration of ESLint-plugin-Meteor into Atom. Find out more in the integration guide.



Install ESLint and this plugin either locally or globally.

$ npm install eslint --save-dev
$ npm install eslint-plugin-meteor --save-dev


Create an .eslintrc.json file with this content at the root of your project:

  "plugins": ["meteor"],
  "extends": ["plugin:meteor/recommended"]

For a more thorough introduction, read the setup guide.

An article with detailed setup instructions can be found here.

List of supported rules

Best Practices

Core API

  • currently no rules implemented

Any rule idea is welcome !

Recommended Configuration

This plugin exports a recommended configuration which enforces good Meteor practices. The rules enabled in this configuration can be found in lib/index.js.

To enable the recommended configuration use the extends property in your .eslintrc.json config file:

  "plugins": [
  "extends": ["eslint:recommended", "plugin:meteor/recommended"]

You probably also want to enable ESLint to parse ECMAScript 2015 and to support React templates.

Add the following to your .eslintrc.json config file

  "parserOptions": {
    "ecmaVersion": 6,
    "sourceType": "module",
    "ecmaFeatures": {
        "jsx": true

See ESLint documentation for more information about extending configuration files.


ESLint-plugin-Meteor is not aware of where files are going to be executed, to keep the plugin simple. It will not warn when accessing client-only features on the server and vice versa.


Read about set up of the development environment.


This plugin is inspired by eslint-plugin-react.


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