# @batterii/eslint-config-vurvey

> Base lint configuration for Vurvey TypeScript projects

Latest version **2.0.0** (published 2026-07-31) · MIT license · 0 weekly downloads

## Install

```sh
npm install @batterii/eslint-config-vurvey
pnpm add @batterii/eslint-config-vurvey
yarn add @batterii/eslint-config-vurvey
bun add @batterii/eslint-config-vurvey
```

## Health

**Score 60/100 (C)** — status: active.

Positive: esm support; no vulnerabilities; recently updated; high maintenance score.

Warnings: low downloads; no types.

## Facts

| | |
|---|---|
| Version | 2.0.0 |
| Published | 2026-07-31 |
| First published | 2021-10-26 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | ESM + CommonJS |
| Dependencies | 0 |
| Unpacked size | 10.2 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 0 |
| Author | Batterii, LLC |
| Maintainers | jroell88, sivarita, sripberger, noahtheduke, mdkiemle, ericziegler, batterii-ci, vssrcj, franceschina, mikoscz_selleo, czikarito, jswob.selleo, mlampe, ericpoff, carterpohl, adelapaz33, thomas-vurvey, hyrumwhite |

## Links

- npm: https://www.npmjs.com/package/@batterii/eslint-config-vurvey
- Repository: https://github.com/Batterii/eslint-config-vurvey
- Homepage: https://github.com/Batterii/eslint-config-vurvey#readme
- Issues: https://github.com/Batterii/eslint-config-vurvey/issues
- npm.io page: https://npm.io/package/@batterii/eslint-config-vurvey

## Recent versions

- 2.0.0 (latest) — 2026-07-31
- 1.1.5 — 2026-05-06
- 1.1.4 — 2026-04-03
- 1.1.3 — 2026-03-30
- 1.1.2 — 2026-03-27
- 1.1.1 — 2026-03-24
- 1.1.0 — 2026-03-24
- 1.0.4 — 2026-01-21
- 1.0.3 — 2025-12-17
- 1.0.2 — 2025-12-12
- 1.0.1 — 2025-12-09
- 1.0.0 — 2025-12-08
- 0.3.9 — 2023-05-16
- 0.3.8 — 2022-06-10
- 0.3.7 — 2022-05-06
- … 11 more at https://npm.io/package/@batterii/eslint-config-vurvey/versions

## README

# @batterii/eslint-config-vurvey

Contains base [Oxlint][oxlint] configurations for all Vurvey TypeScript projects. These
configurations are extended by environment-specific configurations in the
following packages:

- @batterii/eslint-config-vurvey (this package) for Node.js projects.
- [@batterii/eslint-config-vurvey-react][react-config] for React projects.

Any rules which should be enforced in both of our application environments-- as well as in
environment-agnostic projects-- should be configured in this package.

## Usage

1. Create a .oxlintrc.json
2. Extend the .oxlintrc.json from your repo

```json
{
  "extends": ["node_modules/@batterii/eslint-config-vurvey/oxlint/.oxlintrc.json"],
  "rules": {
    "additional": "rules"
  }
}
```

## Scripts

```json
{
  "scripts": {
    "lint": "oxlint .",
    "lintf": "oxlint . --fix"
  }
}
```

## Proposing Changes

Linter rules like these are a team effort-- especially ones that are re-used between two different
teams working in two very different environments. All developers subject to these rules should feel
free to propose changes so that we can arrive at 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.

## 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
version number commit 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][semver] should be made if one or
more rule changes has the potential to produce new linter errors (not warnings) which cannot be
auto-fixed by Lint's `--fix` flag.

If a breaking release of this package is made, breaking releases of all dependent
environment-specific config packages should be made as well. Doing this will enable developers of
affected repositories to upgrade to the breaking versions and address the new errors when they are
able.

## Note on Peer Dependencies

We use peer dependencies rather than direct dependencies. This expresses compatibility
limitations while still ultimately leaving control over Oxlint and its plugins to the repositories
where Oxlint will actually be run.

For more information about this approach, see [this Node.js blog post][peer-deps-blog] on the
subject.

[oxlint]: https://oxc.rs/
[peer-deps]: https://docs.npmjs.com/cli/v7/configuring-npm/package-json#peerdependencies
[peer-deps-blog]: https://nodejs.org/en/blog/npm/peer-dependencies/
[react-config]: https://github.com/Batterii/eslint-config-vurvey-react
[semver]: https://semver.org/

---
_Source: https://npm.io/package/@batterii/eslint-config-vurvey · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._