๐งช Experimental
Use this preset when you want every stable rule from all plus lower-confidence candidate rules that are still being evaluated.
Config keyโ
typefest.configs.experimental
Flat Config exampleโ
import typefest from "eslint-plugin-typefest";
export default [typefest.configs.experimental];
This preset does require type information, because it layers experimental rules on top of all.
Use it when you want to trial report-only or still-maturing rules before they graduate into stable presets.
When to use this presetโ
- You want every stable rule from
all. - You are comfortable reviewing noisier report-only diagnostics.
- You want early visibility into candidate migrations such as
objectMapValues.
Rollout adviceโ
Treat this preset as a proving ground:
- Start with
warnin one package or folder. - Measure noise and collect false-positive feedback.
- Promote only the rules your team finds consistently useful.
Why some candidates were skippedโ
Not every uncovered type-fest or ts-extras helper becomes an experimental rule immediately.
- Some candidates have a clear canonical matcher and are good fits for report-only experimentation.
- Others are intentionally skipped because their hand-written equivalents are too varied or too semantic to lint accurately yet.
Current intentionally skipped examples include SetParameterType, Jsonify, SimplifyDeep, Entry, Entries, isPropertyDefined, and isPropertyPresent.
Maintainer policy for that decision is documented in ADR 0016: Experimental rule admission and skip criteria.
Rules in this presetโ
Fixlegend:๐ง= autofixable๐ก= suggestions availableโ= report only