@kitschpatrol/mdat-config v5.5.0

@kitschpatrol/mdat-config

MDAT configuration for @kitschpatrol/shared-config.

Overview

It's a shared MDAT (Markdown Autophagic Template) system config, plus a command-line tool kpi-mdat to perform mdat-related project initialization, linting, and fixing.

!IMPORTANT

You can use this package on its own, but it's recommended to use @kitschpatrol/shared-config instead for a single-dependency and single-package approach to linting and fixing your project.

This package is included as a dependency in @kitschpatrol/shared-config, which also automatically invokes the command line functionality in this package via its kpi command

Setup

To use just mdat-config in isolation:

1. Install the .npmrc in your project root. This is required for correct PNPM behavior:

   pnpm dlx @kitschpatrol/repo-config init

2. Add the package:

   pnpm add -D @kitschpatrol/mdat-config

3. Add the starter .mdatrc.ts file to your project root, and add any customizations you'd like:

   pnpm exec kpi-mdat init

Usage

The mdat binary is specified as a peer dependency, and should be installed up automatically by PNPM.

You can call it directly, or use the script bundled with the config.

Integrate with your package.json scripts as you see fit, for example:

{
  "scripts": {
    "lint": "kpi-mdat lint",
    "fix": "kpi-mdat fix"
  }
}

"Fix" in this case is a slight misnomer for consistency with the other shared-config tools.

It runs mdat readme expand to expand placeholder comments in your readme.md using the bundled mdat readme expansion rules, plus custom rules provided by mdat-config's mdat.config.ts file, plus any additional rules specified in the repository-specific .mdatrc.ts file.

Configuration

To create a mdat.config.ts in your project root:

pnpm exec kpi-mdat init

(Note that this will delete the mdat property in your package.json!)

Or

To create a mdat property in package.json:

pnpm exec kpi-mdat init --location package

(Note that this will delete the mdat.config.ts file in your project root!)

CLI

Command: kpi-mdat

Kitschpatrol's Mdat shared configuration tools.

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

Usage:

kpi-mdat <command>

See the sections below for more information on each subcommand.

Subcommand: kpi-mdat init

Initialize by copying starter config files to your project root or to your package.json file.

Usage:

kpi-mdat init

Subcommand: kpi-mdat lint

Validate that all Mdat content placeholders in your readme.md file(s) have been expanded. Package-scoped. In a monorepo, it will also run in all packages below the current working directory.

Usage:

kpi-mdat lint

Subcommand: kpi-mdat fix

Expand all Mdat content placeholders in your readme.md file(s). Package-scoped. In a monorepo, it will also run in all packages below the current working directory.

Usage:

kpi-mdat fix

Subcommand: kpi-mdat print-config

Print the effective Mdat configuration. Package-scoped.. Searches up to the root of a monorepo if necessary.. Includes configuration provided by the mdat readme command.

Usage:

kpi-mdat print-config

License

MIT © Eric Mika