@nextcapital/eslint-config

A series of ESLint configs to enforce Nextcapial's code standards.

Installation

npx install-peerdeps --dev @nextcapital/eslint-config

Usage

We export multiple ESLint configurations for your usage.

Base Config (@nextcapital/eslint-config)

This config contains all rules for base JavaScript development - no jest, jsdoc, react, typescript, etc.

// eslint.config.cjs
const nextcapitalBase = require('@nextcapital/eslint-config');

module.exports = [
  ...nextcapitalBase,
  // ......
];

// eslint.config.mjs
import nextcapitalBase from '@nextcapital/eslint-config';

export default [
  ...nextcapitalBase,
  // ......
];

Jest

This config contains all rules for testing with jest. This config does not extend the base config and can be used as a standalone ruleset.

// eslint.config.cjs
const jestConfig = require('@nextcapital/eslint-config/jest');

module.exports = [
  ...jestConfig,
  // ......
];

// eslint.config.mjs
import jestConfig from '@nextcapital/eslint-config/jest';

export default [
  ...jestConfig,
  // ......
];

JSDoc

This config contains all rules for testing with JSDoc. This config does not extend the base config and can be used as a standalone ruleset.

// eslint.config.cjs
const jsdocConfig = require('@nextcapital/eslint-config/jsdoc');

module.exports = [
  ...jsdocConfig,
  // ......
];

// eslint.config.mjs
import jsdocConfig from '@nextcapital/eslint-config/jsdoc';

export default [
  ...jsdocConfig,
  // ......
];

React

This config contains all rules for developing with React/jsx. This config does not extend the base config and can be used as a standalone ruleset.

// eslint.config.cjs
const reactConfig = require('@nextcapital/eslint-config/react');

module.exports = [
  ...reactConfig,
  // ......
];

// eslint.config.mjs
import reactConfig from '@nextcapital/eslint-config/react';

export default [
  ...reactConfig,
  // ......
];

TypeScript

See @nextcapital/eslint-config-typescript.

Contributing

See CONTRIBUTING.md

Publishing

IMPORTANT: Versioning is handled by GitHub Actions through the publish.yml workflow configuration. DO NOT ATTEMPT TO PUBLISH PACKAGES YOURSELF. Publishing yourself should fail anyways because you need the auth token for an npm user in the @nextcapital organization on npm. This section simply documents how the CI workflow works.

Maintainers

Mike Kreiser (@nc-kreiserm)