Stop the language server from considering *-px as canonical form of *-0.25 #20432

There's no per-case opt-out for this rule today — suggestCanonicalClasses is a single global lint setting. Your options:

Option 1: disable the diagnostic, scoped to this project

The setting can live in the workspace-level .vscode/settings.json, so it only affects this project and not your other Tailwind codebases:

{
  "tailwindCSS.lint.suggestCanonicalClasses": "ignore"
}

Option 2: disable the dynamic spacing scale (root cause)

The suggestion exists because v4 derives all spacing utilities from one scaling factor:

@theme {
  --spacing: 0.25rem;
}

That's why px-0.25 (→ 0.0625rem) is considered the "canonical" form of px-px. If you only want explicit spacing tokens in your design system, you can turn the dynamic scale off and define individual keys:

@theme {
  --spacing: initial;
  --spacing-1: 0.25rem;
  --spacing-2: 0.5rem;
  /* ... */
}

With the dynamic scale disabled, px-0.25 no longer resolves to anything, so the suggestion disappears entirely — while keeping the rest of the lint rules active.

For the record, the Tailwind team has confirmed this behavior is intentional; see tailwindlabs/tailwindcss-intellisense#1527 for the maintainer's explanation.

Your underlying point (that 1px and 0.0625rem behave differently when the root font-size changes) is fair — if you'd like per-rule granularity (e.g. exempting *-px specifically), that would be a feature request for tailwindcss-intellisense.