• Installation
• Usage
• Publishing

This library has a required peerDependencies for eslint

Follow the Github Packages setup instructions.

$ npm install --save-dev @arcadiapower/eslint-config

Follow the Gemfury setup instructions.

$ npm intsall --save-dev eslint-config-arcadia

Extend your .eslintrc.js:

module.exports = {
  extends: '@arcadiapower', // For Gemfury installations, use "arcadia"
  rules: {
    // your overrides
  },
};

This config also exposes a React-specific config, which is intended for apps that use React.

module.exports = {
  extends: '@arcadiapower/eslint-config/react', // For Gemfury installations, use "arcadia/react"
};

Note: Due to this bug you need to have associated plugins installed to make things work. Add them as dependencies to your project:

• react: React JS library eslint-plugin-react for rules regarding React (needed in the react config)
• jsx-a11y: eslint-plugin-jsx-a11y for rules regarding accessibility with JSX (needed in the react config)
• @typescript-eslint: @typescript-eslint/parser and @typescript-eslint/eslint-plugin (needed for projects written in TypeScript)

The config is hosted as an NPM package on Github Packages, with legacy support for Gemfury.

To publish a new version after your pull request is merged, go to the releases page and draft a new release. This will automatically kick off the publish workflow.

1. In your pull request, bump the version.
2. After merging, pull master and run npm pack
3. Upload the resulting package on the Gemfury dashboard.