{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "label",
  "type": "registry:ui",
  "title": "Label",
  "files": [
    {
      "path": "ui/label.tsrx",
      "type": "registry:ui",
      "target": "components/ui/label.tsrx",
      "content": "// Base UI base label — a plain host `<label>`.\n//\n// NOT `Field.Label`, and that is the whole point of this file. Base UI's label part is\n// `Field.Label`, but it calls `useFieldRootContext(false)` — it HARD-REQUIRES a `<Field.Root>`\n// ancestor and throws \"FieldRootContext is missing\" without one. Upstream's own FieldLabel does\n// the same, so that is faithful behavior, not a porting defect.\n//\n// shadcn's `Label`, by contrast, is a standalone component: the docs use it beside an Input with\n// no Field wrapper at all, which is exactly how the playground uses it. Routing it through\n// `Field.Label` made every such use a runtime crash. A plain `<label>` works standalone AND\n// inside a Field, and consumers who want Base UI's automatic label/control association can reach\n// for `Field.Label` directly.\n//\n// Regression coverage: `tests/base-ui-standalone.test.ts`.\n//\n// UNVERIFIED PROVENANCE: the class string is taken from this package's React Aria base rather\n// than transcribed from upstream's Base UI source. It carries one utility the Radix base omits\n// (`peer-data-disabled:opacity-50`).\nimport { cn } from '@/lib/utils';\nimport type { HostProps } from '@/lib/types';\n\nexport function Label({ className, ...props }: HostProps<'label'>) @{\n\t<label\n\t\tdata-slot=\"label\"\n\t\tclassName={cn(\n\t\t\t'flex items-center gap-2 text-sm leading-none font-medium select-none group-data-[disabled=true]:pointer-events-none group-data-[disabled=true]:opacity-50 peer-disabled:cursor-not-allowed peer-disabled:opacity-50 peer-data-disabled:opacity-50',\n\t\t\tclassName,\n\t\t)}\n\t\t{...props}\n\t/>\n}\n"
    }
  ],
  "registryDependencies": [
    "@octane/types",
    "@octane/utils"
  ]
}