Textarea Autosize
Free · MITHeadless, accessible, and styled entirely through the attribute surface below — bring your own CSS system, or start from the reference theme.
Install
Without a flag you get no styling at all — plain HTML carrying the attribute surface below. --theme copies the same theme in two dialects;--bridge lumos re-points either one onto Lumos for Astro's tokens (it needs a theme to re-point, and Lumos itself, already in your project).
Unstyled — behavior only, you write the CSS
npx astrocraft-ui add forms/textarea-autosizePlain-CSS theme — no build step
npx astrocraft-ui add forms/textarea-autosize --theme cssTailwind theme — needs Tailwind v4
npx astrocraft-ui add forms/textarea-autosize --theme tailwindPlain-CSS theme, re-pointed onto Lumos tokens
npx astrocraft-ui add forms/textarea-autosize --theme css --bridge lumosTailwind theme, re-pointed onto Lumos tokens
npx astrocraft-ui add forms/textarea-autosize --theme tailwind --bridge lumosLive demo
Submitting: error summary, autosize, character count
Submit it empty: the summary appears, takes focus, and links to the first field that failed. Fill it in and the button goes aria-busy exactly once. The bio grows as you type and the counter only speaks up near the limit.
Attribute surface
With no class-merging machinery, these attributes are the whole extension point. State is a data-attribute or a native attribute; visibility is the hiddenattribute. Generated from source by pnpm slots.
| Component | Slots | Variants | Runtime state | Native state |
|---|---|---|---|---|
| `TextareaAutosize.astro` | `textarea-autosize` | `data-size`: `sm` · `md` · `lg` `data-state`: `default` · `error` · `success` | — | — |
Source
What the command copies — 2 files, alias-free so the copy lands standing alone. This is the whole component; there is nothing else.
---
// src/components/ui/forms/textarea-autosize/TextareaAutosize.astro — headless primitive (see ../../README.md).
// A <textarea> that grows with its content. The platform does this natively now — `field-sizing:
// content`, which structure.css sets — so the first choice here is one CSS declaration and no script
// at all: no measuring, no reflow, no layout thrash, and it works before any JavaScript loads.
//
// The bundled script is a FALLBACK and checks for that support before doing anything, so on a browser
// with `field-sizing` it adds exactly one `CSS.supports` call and then gets out of the way. Where it
// does run, it is the classic reset-then-measure (`height: auto` before reading `scrollHeight`),
// because a textarea's `scrollHeight` never shrinks below its current height.
//
// Both paths write an inline style, never a class (contract rule 4). Mirrors Textarea's `data-size` /
// `data-state` field surface; `rows` is still the minimum height, and a `max-height` in your theme is
// still respected by both paths.
import "../../../../styles/structure.css";
import type { HTMLAttributes } from "astro/types";
type Props = HTMLAttributes<"textarea"> & {
size?: "sm" | "md" | "lg";
state?: "default" | "error" | "success";
};
const { size = "md", state = "default", class: className, ...rest } = Astro.props;
---
<textarea
class={className}
data-slot="textarea-autosize"
data-size={size}
data-state={state}
{...rest}></textarea>
<script>
import { onReadyOnce } from "../../_once";
const NATIVE = CSS.supports("field-sizing", "content");
function wire(element: HTMLElement) {
if (NATIVE || !(element instanceof HTMLTextAreaElement)) return;
const fit = () => {
// The scrollbar would flash on every keystroke between the reset and the new height.
element.style.overflowY = "hidden";
element.style.height = "auto";
element.style.height = `${element.scrollHeight}px`;
};
element.addEventListener("input", fit);
fit();
}
onReadyOnce('[data-slot="textarea-autosize"]', wire);
</script>
import TextareaAutosize from "./TextareaAutosize.astro";
export { TextareaAutosize };
export default TextareaAutosize;
What you get
The component source, copied into your project by npx astrocraft-ui add forms/textarea-autosize — no package dependency, no CSS to fight. Whatever the paid blocks compose, this is it.