@milkyskies/biome-config

Shared Biome config + GritQL plugins for milkyskies TypeScript projects.

What's in it

• biome.json — formatter (tab indent, double quotes, no semicolons, line width 100) + linter (recommended + noExplicitAny: error) + import organizer.
• plugins/no-as-cast.grit — bans as type assertions. Allowed: as const, import { x as y }, import * as ns. Suppress one-off legitimate cases with // biome-ignore lint/plugin: <reason>.

Use it

Install from npm:

bun add -d @milkyskies/biome-config @biomejs/biome
# or: pnpm add -D @milkyskies/biome-config @biomejs/biome

Add a project biome.json that extends the base — the GritQL plugin comes along automatically:

{
	"$schema": "https://biomejs.dev/schemas/2.4.15/schema.json",
	"extends": ["@milkyskies/biome-config/biome.json"]
}

The shared config declares the plugin as ./node_modules/@milkyskies/biome-config/plugins/no-as-cast.grit. Biome resolves that path relative to the consumer's biome.json, so it picks up the plugin from the consumer's own node_modules — no consumer-side boilerplate.

Caveat: assumes pnpm or bun (or any package manager that puts a per-package node_modules/@milkyskies/biome-config next to the consumer). Plain hoisted-at-root npm with nested apps/*/biome.json may not resolve until biome adds bare-specifier support in plugins.

Add scripts to your project package.json:

{
	"scripts": {
		"check": "biome check --write",
		"format": "biome format --write",
		"lint": "biome lint"
	}
}

Agents writing code in projects that consume this config should run bun run check before claiming work done.

Why a separate repo

Published from its own repo so any TS project (monorepo or single-app) can depend on it via npm without forcing a milky-kit workspace layout. milky-kit consumes this as a regular npm devDependency in its template scaffolds.