rulebearing-rules

Rulebearing's framework presets as a versioned library, published with every Rulebearing release at the release version to npm (rulebearing-rules), NuGet (Rulebearing.Rules) and PyPI (rulebearing-rules). Install it from whichever registry your repository already uses, then extend a preset by the same name everywhere. Source, documentation and releases: https://github.com/benbahrenburg/rulebearing

npm install --save-dev rulebearing-rules          # node_modules/rulebearing-rules/
dotnet add package Rulebearing.Rules              # the NuGet global packages folder, after restore
pip install rulebearing-rules                     # site-packages/rulebearing_rules/

extends: [rulebearing:typescript, rulebearing:recommended, rulebearing-rules/nextjs]

Rulebearing looks for the package in node_modules/, then the NuGet global packages folder, then a Python environment's site-packages (docs/config.md). The binary bundles the same files as rulebearing:<preset>; the package lets a repository pin the rules' version through its package manager.

Each framework preset is an opinion, not a default. Nothing extends one unless a configuration names it (design § The developer relations hat: "off by default, each a documented opinion"). Every rule's comment carries a decision token, and every rule's examples pass rulebearing test, which this repository's CI runs on each preset. What each preset forbids, and what it leaves out on purpose, is in presets/frameworks/README.md.

MIT licence.

How the packages are built

The presets live once, in presets/frameworks/ and presets/rulebearing/recommended.yaml; this folder holds the three package definitions and no copy of them (ADR-0071, FR-REACH-04, plan 0003 Step 23). pack.sh packs them at one version; the committed metadata carries none, and nothing in the source tree is edited.

wrappers/rules/pack.sh <version> <out-dir> [npm] [nuget] [pypi]   # none named: all three

The release workflow calls it from its existing packing jobs, install-checks each package on macOS, Linux and Windows by resolving extends: rulebearing-rules/nextjs from it, and publishes it beside the other packages (docs/release.md). pytest wrappers/rules --cov=wrappers/rules tests the hook and packs all three packages, then resolves the preset from each installed layout with the binary built from this checkout.