@batterii/eslint-config-vurvey-react

Contains Oxlint configuration for Vurvey React projects. This configuration base configurations located in @batterii/eslint-config-vurvey.

Usage

To use this config, first install it and its peer dependencies. Then, create a file called .oxlintrc.json at the root of the repository with the following contents:

Note: a packaged config can't extend another package, so we flatten the base lint package into the extends array

{
  "$schema": "./node_modules/oxlint/configuration_schema.json",
  "extends": [
    "node_modules/@batterii/eslint-config-vurvey/oxlint/.oxlintrc.json",
    "node_modules/@batterii/eslint-config-vurvey-react/oxlint/.oxlintrc.json"
  ],
  "ignorePatterns": [],
  "overrides": []
}

Next, create scripts in your package.json for running the linter:

{
  "scripts": {
    "lint": "oxlint . --type-aware",
    "lintf": "oxlint . --fix --type-aware"
  }
}

Running these scripts will lint all applicable files in the repo based on the configuration.

If needed on a per-project basis, you can make changes to the configuration within the .oxlintrc.json file by extending or modifying the exported config array. As a general rule, however, shareable configuration should be preferred to help ensure code style consistency between different repositories.

Proposing Changes

Linter rules like these are a team effort. All developers subject to these rules should feel free to propose changes so that we can arrive a set of common rules that work for everyone. To do this, simply open a pull request and give other affected devs the opportunity to discuss in comments.

For organization and tracking purposes, pull requests to this repo should focus on changing a small number of rules at a time. This will help keep discussion focused on individual conventions and concerns.

Note that the rules in this repo only affect our front end React repositories. In order to make changes to common rules, see @batterii/eslint-config-vurvey.

Publishing

npm version and npm publish can be used to publish this package as normal. These should be run in the latest main branch by someone with write access to the package on NPM. When doing so, a preversion script will lint the repo and a prepublishOnly script will automatically push the verison number commmit and tag to the GitHub repo.

Note that lint configuration changes can have massive effects on other developers and code bases. When publishing a new version of this package, a breaking release should be made if one or more rules changes has the potential to produce new linter errors (not warnings) which cannot be auto-fixed by the lint provider's --fix flag.

Doing this will enable developers of affected repositories to upgrade to the breaking versions and address the new errors when they are able.