Configs

The package exports three shareable configs for staged adoption:

• 🟡 container-query-recommended — low-noise baseline for named containers and impossible ranges.
• 🔴 container-query-strict — full policy for teams that want explicit containment contracts and tokenized breakpoints.
• 🟣 container-query-all — complete public rule catalog. It currently matches strict because every non-recommended rule is intentionally strict.

Use them from containerQuerySanityPluginConfigs or from extends subpath exports.

Preset matrix

Legend: ✅ = enabled · — = not enabled

Rule	🟡 Recommended	🔴 Strict	🟣 All
no-block-axis-query-on-inline-size-container	—	✅	✅
no-conflicting-container-name-declarations	—	✅	✅
no-degenerate-container-query-conditions	—	✅	✅
no-invalid-container-query-ranges	✅	✅	✅
no-scroll-state-query-on-non-scroll-state-container	—	✅	✅
no-size-query-on-non-size-container	—	✅	✅
no-unknown-container-names	—	✅	✅
no-unreachable-container-intervals	✅	✅	✅
prefer-logical-size-features	—	✅	✅
prefer-range-syntax	—	✅	✅
require-breakpoint-token-usage	—	✅	✅
require-container-type-for-named-containers	—	✅	✅
require-named-container	✅	✅	✅

Which config should I use?

• Start with 🟡 container-query-recommended when introducing the plugin into an existing codebase.
• Move to 🔴 container-query-strict when every component should declare reliable container contracts and tokenized query thresholds.
• Use 🟣 container-query-all when you want a config that always follows the complete public rule surface.

Related docs

• Getting Started
• Overview
• Current Status