Data

Tools

Indexes

Applications

Experiments

Awesome

An open API service indexing awesome lists of open source software.

https://github.com/kitschpatrol/shared-config

A single dependency and single command to configure and run various code linters and tools.
https://github.com/kitschpatrol/shared-config

cli cspell eslint-config github-actions kpi mdat npm-package prettier-config remark-config remark-lint shared-config stylelint-config tsconfig typescript-config

Last synced: 6 months ago
JSON representation

A single dependency and single command to configure and run various code linters and tools.

Awesome Lists containing this project

README 

          



# 🔬 @kitschpatrol/shared-config



[![NPM Package @kitschpatrol/shared-config](https://img.shields.io/npm/v/@kitschpatrol/shared-config.svg)](https://npmjs.com/package/@kitschpatrol/shared-config)

[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)



**A collection of shared configurations, linters, and formatting tools for TypeScript projects. All managed as a single dependency, and invoked via a single CLI command.**



## Table of contents



- [Overview](#overview)

- [Getting started](#getting-started)

- [Usage](#usage)

- [Implementation notes](#implementation-notes)

- [Development notes](#development-notes)

- [Background](#background)

- [License](#license)



## Overview



This project attempts to consolidate most of the configuration and tooling shared by my open-source and internal TypeScript / Node based projects into a single dependency with a single CLI meta-command to lint and fix issues.



By installing `@kitschpatrol/shared-config` and then running `kpi`, you can run a half-dozen pre-configured code quality and linting tools in one shot. This spares you from cluttering your project's `devDependencies` with packages tangential to the task at hand.



If you don't plan to customize tool configurations, `@kitschpatrol/shared-config init` exposes an option to store references to each tool's shared configuration in your `package.json` instead of in files in your project root (at least where permitted by the tool). This can save a bit of file clutter in your project's root directory, at the expense of the immediate discoverability of the tools.



In addition, each tool exports a typed configuration factory function to simplify specifying and extending the default configuration.



The command name `kpi` might stand for "Kitschpatrol Project Inspector", or the more McKinseyan "Key Performance Indicators".



### Tools



It takes care of dependencies, configuration, invocation, and reporting for the following tools:



- [ESLint](https://eslint.org) (including Svelte, Astro, React, and TypeScript support — including type-checked rules)

- [Prettier](https://prettier.io) (including a bunch of extra plugins)

- [Stylelint](https://stylelint.io)

- [TypeScript](https://www.typescriptlang.org/) (including a shared TSConfig)

- [CSpell](https://cspell.org) (bundled with a number of custom dictionaries, and a custom unused-word detector)

- [Case Police](https://github.com/antfu/case-police)

- [Knip](https://knip.dev/)

- [VS Code](https://code.visualstudio.com) (extension recommendations and extension settings)

- [Mdat](https://github.com/kitschpatrol/mdat) (my markdown templating and expansion tool)

- [remarklint](https://github.com/remarkjs/remark-lint)

- Basic repo boilerplate (`.npmrc`, `.gitignore`, etc.)



### Packages



This particular readme is for the [`@kitschpatrol/shared-config`](https://www.npmjs.com/package/@kitschpatrol/shared-config) package, which depends on a number of tool-specific packages included in the [`kitschpatrol/shared-config`](https://github.com/kitschpatrol/shared-config) monorepo on GitHub, each of which is documented in additional detail in its respective readme.



#### Primary package



- [`@kitschpatrol/shared-config`](https://github.com/kitschpatrol/shared-config/blob/main/packages/shared-config/readme.md) (`kpi` command)



#### Sub-packages



- [`@kitschpatrol/cspell-config`](https://github.com/kitschpatrol/shared-config/blob/main/packages/cspell-config/readme.md) (`kpi-cspell` command)

- [`@kitschpatrol/eslint-config`](https://github.com/kitschpatrol/shared-config/blob/main/packages/eslint-config/readme.md) (`kpi-eslint` command)

- [`@kitschpatrol/knip-config`](https://github.com/kitschpatrol/shared-config/blob/main/packages/knip-config/readme.md) (`kpi-knip` command)

- [`@kitschpatrol/mdat-config`](https://github.com/kitschpatrol/shared-config/blob/main/packages/mdat-config/readme.md) (`kpi-mdat` command)

- [`@kitschpatrol/prettier-config`](https://github.com/kitschpatrol/shared-config/blob/main/packages/prettier-config/readme.md) (`kpi-prettier` command)

- [`@kitschpatrol/remark-config`](https://github.com/kitschpatrol/shared-config/blob/main/packages/remark-config/readme.md) (`kpi-remark` command)

- [`@kitschpatrol/repo-config`](https://github.com/kitschpatrol/shared-config/blob/main/packages/repo-config/readme.md) (`kpi-repo` command)

- [`@kitschpatrol/stylelint-config`](https://github.com/kitschpatrol/shared-config/blob/main/packages/stylelint-config/readme.md) (`kpi-stylelint` command)

- [`@kitschpatrol/typescript-config`](https://github.com/kitschpatrol/shared-config/blob/main/packages/typescript-config/readme.md) (`kpi-typescript` command)



> [!IMPORTANT]

>

> Any of these packages may be installed and run on their own via CLI if desired. However, in general, the idea is to use `@kitschpatrol/shared-config` to easily run them all simultaneously over a repo with a single command with options to either check or (where possible) fix problems, with output aggregated into a single report.



Running `kpi ` calls the same command across the entire collection of sub-packages.



So assuming you've installed `@kitschpatrol/shared-config`...



Running:



```sh

kpi init

```



Is the same as running:



```sh

kpi-repo init

kpi-mdat init

kpi-typescript init

kpi-eslint init

kpi-stylelint init

kpi-cspell init

kpi-knip init

kpi-remark init

kpi-prettier init

```



_(Sub-commands are always executed in the above order.)_



The top-level `kpi` command also takes care of some nuances in terms of _which_ sub-packages implement _which_ commands, and which subcommands take arguments.



## Getting started



### Dependencies



[Node](https://nodejs.org) >=20.9.0 is required, and [pnpm](https://pnpm.io) >=10 is recommended. NPM and yarn might work as well, but I haven't tested them.



### Installation



#### Quick start from scratch:



Bootstrap a new project and open in VS Code:



```sh

git init && pnpm init && pnpm pkg set type="module" && pnpm dlx @kitschpatrol/repo-config init && pnpm add -D @kitschpatrol/shared-config && pnpm kpi init && pnpm i && code .

```



Note that `kpi init` takes an optional `--location package` flag will put as much configuration in your `package.json` as possible instead of creating discrete config files in your project root for each tool. Putting config in `package.json` can save some clutter, but can make it clunkier to extend or customize configurations.



At any point, you can call `kpi init` again with the `--location package` or `--location file` flag to reinitialize your configuration files in one place or the other and restore the default configurations.



#### Quick add to an existing project:



This might overwrite certain config files, so commit first:



```sh

pnpm dlx @kitschpatrol/repo-config init && pnpm i && pnpm add -D @kitschpatrol/shared-config && pnpm kpi init

```



#### Step-by-step:



1. Install the requisite `.npmrc`:



   ```sh

   pnpm dlx @kitschpatrol/repo-config init

   ```



2. Install the package:



   ```sh

   pnpm add -D @kitschpatrol/shared-config

   ```



3. Add default config files for all the tools to your project root:



   ```sh

   pnpm kpi init

   ```



   Or, if you don't plan to customize tool configurations, you might want to put as much config as possible under tool-specific keys in 'package.json':



   ```sh

   pnpm kpi init --location package

   ```



4. Add helper scripts to your `package.json`:



   These work a bit like [npm-run-all](https://github.com/mysticatea/npm-run-all) to invoke all of the bundled tools.



   ```json

   {

     "scripts": {

       "fix": "kpi fix",

       "lint": "kpi lint"

     }

   }

   ```



5. Set up GitHub action credentials (if desired)



   The GitHub actions included in @kitschpatrol/repo-config require permissions to create releases and update your repository metadata. You can add these through the GitHub website under the _Settings → Secrets and variables → Actions_ page under the key `PERSONAL_ACCESS_TOKEN`, or with the [GitHub CLI](https://cli.github.com/) and a credential manager like [1Password CLI](https://developer.1password.com/docs/cli/get-started/):



   ```sh

   gh secret set PERSONAL_ACCESS_TOKEN --app actions --body $(op read 'op://Personal/GitHub Mika/PERSONAL_ACCESS_TOKEN')

   ```



   See the [@kitschpatrol/repo-config readme](/packages/repo-config/readme.md#github-configuration) for more details.



## Usage



Various VS Code plugins for the bundled tools should "just work".



To check / lint your entire project, after configuring the `package.json` as shown above:



```sh

pnpm run lint

```



To run all of the tools in a _potentially destructive_ "fix" capacity:



```sh

pnpm run fix

```



### CLI



#### Command: `kpi`



Run aggregated @kitschpatrol/shared-config commands.



This section lists top-level commands for `kpi`.



Usage:



```txt

kpi 

```



| Command        | Argument    | Description                                                                                                                                                                                 |

| -------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

| `init`         |             | Initialize configuration files for the entire suite of @kitschpatrol/shared-config tools. Will use option flags where possible if provided, but some of the invoked tools will ignore them. |

| `lint`         | `[files..]` | Lint your project with multiple tools in one go. Will use file arguments / globs where possible if provided, but some of the invoked tools only operate at the package-scope.               |

| `fix`          | `[files..]` | Fix your project with multiple tools in one go. Will use file arguments / globs where possible if provided, but some of the invoked tools only operate at the package-scope.                |

| `print-config` | `[file]`    | Print aggregated tool configuration data. Will use file arguments / globs where possible if provided, but some of the invoked tools only operate at the package-scope.                      |



| Option              | Description         | Type      |

| ------------------- | ------------------- | --------- |

| `--help`
`-h`    | Show help           | `boolean` |

| `--version`
`-v` | Show version number | `boolean` |



_See the sections below for more information on each subcommand._



#### Subcommand: `kpi init`



Initialize configuration files for the entire suite of @kitschpatrol/shared-config tools. Will use option flags where possible if provided, but some of the invoked tools will ignore them.



Usage:



```txt

kpi init

```



| Option              | Description         | Type                 | Default  |

| ------------------- | ------------------- | -------------------- | -------- |

| `--location`        | TK                  | `"file"` `"package"` | `"file"` |

| `--help`
`-h`    | Show help           | `boolean`            |          |

| `--version`
`-v` | Show version number | `boolean`            |          |



#### Subcommand: `kpi lint`



Lint your project with multiple tools in one go. Will use file arguments / globs where possible if provided, but some of the invoked tools only operate at the package-scope.



Usage:



```txt

kpi lint [files..]

```



| Positional Argument | Description                    | Type    | Default |

| ------------------- | ------------------------------ | ------- | ------- |

| `files`             | Files or glob pattern to lint. | `array` | `[]`    |



| Option              | Description         | Type      |

| ------------------- | ------------------- | --------- |

| `--help`
`-h`    | Show help           | `boolean` |

| `--version`
`-v` | Show version number | `boolean` |



#### Subcommand: `kpi fix`



Fix your project with multiple tools in one go. Will use file arguments / globs where possible if provided, but some of the invoked tools only operate at the package-scope.



Usage:



```txt

kpi fix [files..]

```



| Positional Argument | Description                   | Type    | Default |

| ------------------- | ----------------------------- | ------- | ------- |

| `files`             | Files or glob pattern to fix. | `array` | `[]`    |



| Option              | Description         | Type      |

| ------------------- | ------------------- | --------- |

| `--help`
`-h`    | Show help           | `boolean` |

| `--version`
`-v` | Show version number | `boolean` |



#### Subcommand: `kpi print-config`



Print aggregated tool configuration data. Will use file arguments / globs where possible if provided, but some of the invoked tools only operate at the package-scope.



Usage:



```txt

kpi print-config [file]

```



| Positional Argument | Description                 | Type     |

| ------------------- | --------------------------- | -------- |

| `file`              | File or glob pattern to TK. | `string` |



| Option              | Description         | Type      |

| ------------------- | ------------------- | --------- |

| `--help`
`-h`    | Show help           | `boolean` |

| `--version`
`-v` | Show version number | `boolean` |



Recall that the `@kitschpatrol/shared-config` package aggregates integration and invocation of the other tool-specific packages in this monorepo. Running a cli command on `kpi` effectively runs the same command against all the tool-specific packages.



## Implementation notes



### `check` vs `lint`



This project combines a mix of tools that regard their core task variously as "linting" or "checking" code and prose.



Across all the tools, I've chosen to use the term "lint" instead of "check" to refer to the read-only evaluation process.



### Package architecture



Each package has a simple `/src/cli.ts` file which defines the behavior of its eponymous binary. The build step turns these into node "binary" scripts, providing default implementations where feasible.



The monorepo must be kept intact, as the sub-packages depend on scripts in the parent during build.



### Hoisting caveats



The pnpm authors consider module hoisting harmful, and I tend to agree, but certain exceptions are carved out as necessary and accommodated via the `.npmrc` file included in `@kitschpatrol/repo-config`:



- CSpell, remark, mdat, ESLint, and Prettier all need to be hoisted via `public-hoist-pattern` to be accessible in `pnpm exec` scripts and to VS Code plugins.



- Even basic file-only packages like `repo-config` seem to need to be hoisted via for their bin scripts to be accessible via `pnpm exec`



- In earlier version of pnpm, `prettier` and `eslint` packages were hoisted by default, but as of pnpm 10 this is [no longer the case](https://github.com/pnpm/pnpm/releases/tag/v10.0.0).



## Development notes



The repo uses placeholders for the bin script for each tool to avoid circular dependency issues during `pnpm install`.



To tell git to ignore changes to the placeholders, run `pnpm run bin-ignore`.



For local development via `pnpm`, use `file:` dependency protocol instead of `link:`



Something to investigate: An [approach](https://github.com/antfu/eslint-config#vs-code-support-auto-fix) to ignoring style rules in VS Code, and possibly migrate all style handling to ESLint instead of Prettier.



## Background



### Motivation



[`xo`](https://github.com/xojs/xo) is really, really close to what I'm after here, but I wanted a few extra tools and preferred to use "first party" VS Code plugins where possible.



[`create-typescript-app`](https://github.com/JoshuaKGoldberg/create-typescript-app) is also excellent, and probably the best starting point for most people for most new projects. However, it does not take a "single top-level dependency" / "single unified CLI" approach.



[`antfu/eslint-config`](https://github.com/antfu/eslint-config) and [`@sxzz/eslint-config`](https://github.com/sxzz/eslint-config) inspired the approach to ESLint integration.



### Adjacent projects



- [@voxpelli/eslint-config](https://github.com/voxpelli/eslint-config)

- [1stG/configs](https://github.com/1stG/configs)

- [antfu/eslint-config](https://github.com/antfu/eslint-config)

- [awesome-eslint](https://github.com/dustinspecker/awesome-eslint)

- [create-typescript-app](https://github.com/JoshuaKGoldberg/create-typescript-app)

- [envsa/shared-config](https://github.com/envsa/shared-config) (Liam Rella's fork of `@kitschpatrol/shared-config`)

- [eslint-config-current-thing](https://github.com/GildedPleb/eslint-config-current-thing) _(Smart!)_

- [eslint-config-hyperse](https://github.com/hyperse-io/eslint-config-hyperse)

- [lass](https://lass.js.org) (xo etc.)

- [megalinter](https://github.com/oxsecurity/megalinter) (Multi-language.)

- [neostandard](https://github.com/neostandard/neostandard)

- [NullVoxPopuli/eslint-configs](https://github.com/NullVoxPopuli/eslint-configs)

- [qlty](https://github.com/qltysh/qlty) (Multi-language.)

- [routine-npm-packages](https://github.com/kachkaev/routine-npm-packages) and [example](https://github.com/kachkaev/website)

- [sheriff](https://www.eslint-config-sheriff.dev)

- [standard](https://standardjs.com)

- [sxzz/eslint-config](https://github.com/sxzz/eslint-config)

- [trunk](https://trunk.io)

- [ts-reset](https://github.com/mattpocock/ts-reset)

- [tsconfig/bases](https://github.com/tsconfig/bases/tree/main)

- [vscode-file-nesting-config](https://github.com/antfu/vscode-file-nesting-config)

- [xo](https://github.com/xojs/xo)

- [TanStack Config](https://tanstack.com/config/latest)

- [Complete](https://complete-ts.github.io/)

- [vercel/style-guide](https://github.com/vercel/style-guide)

- [ZumerBox](https://github.com/zumerlab/zumerbox)



## License



[MIT](license.txt) © Eric Mika