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

eslint-plugin-ember-suave

v2.0.1

Published

DockYard's ESLint plugin for Ember apps

Downloads

33,819

Readme

eslint-plugin-ember-suave Build Status

eslint-plugin-ember-suave is built and maintained by DockYard, contact us for expert Ember.js consulting.

This ESLint plugin exports custom linting rules and a recommended configuration based on DockYard's styleguide. It is tailored for Ember apps specifically, and may be used in conjunction with ember-cli-eslint, or with the ESLint CLI.

Using the plugin with Ember CLI

Installation

Install the plugin as a dev dependency in your Ember CLI project.

npm install --save-dev eslint-plugin-ember-suave

This will make the plugin available to ESLint.

Next, install the ember-cli-eslint addon so that your app can be linted during development and testing. This will also uninstall ember-cli-jshint since there is no need to have both linters running at the same time.

ember install ember-cli-eslint

Upgrading from ember-suave

If you are upgrading from ember-suave you will have to make sure that you remove the addon from your project. Otherwise you will have two linters running.

npm uninstall --save-dev ember-suave

Configuration

The ember-cli-eslint addon blueprint generates a .eslintrc.js configuration file at the root of the project. By default, it is set to extend ESLint's recommended subset of core linting rules.

Add the plugin and its recommended configuration to the list of extensions:

// .eslintrc.js

module.exports = {
  // ...
  plugins: [
    'ember',
    'ember-suave'
  ],
  extends: [
    'eslint:recommended',
    'plugin:ember-suave/recommended'
  ],
  rules: {
  }
  // ...
};

Overriding Rules

Both core rules (provided by ESLint) and custom rules (prefixed by ember-suave/) from the plugin's recommended configuration can be turned off or modified, if desired.

// .eslintrc.js

module.exports = {
  // ...
  plugins: [
    'ember',
    'ember-suave'
  ],
  extends: [
    'eslint:recommended',
    'plugin:ember-suave/recommended'
  ],
  rules: {
    'quotes': ['error', 'double'],
    'ember-suave/no-const-outside-module-scope': 'off'
  }
};

Working with Editors and the CLI

If you use ESLint in an editor or from the command line, you'll need to install eslint-plugin-ember-suave globally too.

npm install -g eslint-plugin-ember-suave

Rules

A list of custom rules and documentation can be found here.

Development

The provided Yeoman generator should be used for creating rules. In doing so, each rule will have a rule, documentation and test file created automatically. All rules should be tested!

Tests can be run using npm test. Additionally, AST Explorer is a great way to look into the structure of a node to determine what to expect.

Authors

Contributors

Versioning

This library follows Semantic Versioning

Legal

DockYard, Inc. © 2016

@dockyard

Licensed under the MIT license