Textarea

<loomi-textarea> — a themeable multi-line text input with a floating label and inline validation. Form-associated: its value submits with the surrounding form.

npm install @loomidev/textarea lit

import "@loomidev/textarea";

Basic Usage

By default the textarea renders with three rows. Use placeholder for simple hint text.

<loomi-textarea placeholder="Comment"></loomi-textarea>

With Labels

Set label instead of (or together with) placeholder for a label that sits as placeholder text until the field is focused, then floats to the top border — a compact way to build forms without separate <label> elements taking up space.

<loomi-textarea label="Comment"></loomi-textarea>

Required Fields

Marks the field with a red asterisk next to the label/placeholder, and fails validate() while empty.

<loomi-textarea required label="Comment"></loomi-textarea>

Rows & Resizing

Increase rows to make the textarea taller by default.

<loomi-textarea label="Bio" rows="6"></loomi-textarea>

Validation

validate() returns true/false and, with show-error-inline, renders error-message directly beneath the field instead of you wiring up your own error UI.

<loomi-textarea
  required
  label="Bio"
  error-message="Write something about yourself"
  show-error-inline
></loomi-textarea>

<script type="module">
  const el = document.querySelector("loomi-textarea");
  submitButton.addEventListener("click", () => {
    if (!el.validate()) return;
    // proceed
  });
</script>

Mention Picker

Set mention-triggers (JSON array of trigger characters) and the mentionData property (a map of trigger → items) to enable an inline @mention-style autocomplete picker. The panel opens when the user types a trigger character at a word boundary — so foo@bar.com does not open it, but hi @bar does.

<loomi-textarea
  id="comments"
  label="Write a comment — try @, # or /"
  rows="4"
  mention-triggers='["@","#","/"]'
></loomi-textarea>

<script type="module">
  const el = document.getElementById("comments");

  // Supply items per trigger character.
  el.mentionData = {
    "@": [
      { label: "emma.reid",  description: "Emma Reid" },
      { label: "chris.b",    description: "Chris Brooks" },
    ],
    "#": [
      { label: "bug" },
      { label: "design" },
    ],
    "/": [
      { label: "assign", description: "Assign to someone" },
      { label: "close",  description: "Close this thread" },
    ],
  };

  // Fired while the user types after a trigger — use to load items asynchronously.
  el.addEventListener("loomi-mention-search", (e) => {
    const { trigger, query } = e.detail;
    // fetch and reassign el.mentionData[trigger] if needed
  });

  // Fired when the user picks an item.
  el.addEventListener("loomi-mention-select", (e) => {
    const { trigger, item } = e.detail;
    console.log("selected", trigger, item);
  });
</script>

Each item in mentionData accepts these fields:

Field	Type	Description
label	string	Required. Inserted into the textarea as trigger + label + " ".
value	string?	Opaque value included in loomi-mention-select detail.
description	string?	Secondary text shown on the right of the item.
image	string?	URL of an avatar/icon shown on the left.

Keyboard navigation: ↑/↓ to move, Enter or Tab to confirm, Escape to close. The picker closes automatically when clicking outside or scrolling.

Field appearance

Use variant="minimal" for a bottom-border-only field:

<loomi-textarea label="Message" variant="minimal"></loomi-textarea>

Use label-position="inside" to keep a compact label inside the top of the field, with the entered text displayed beneath it:

<loomi-textarea label="Message" label-position="inside"></loomi-textarea>

Accessibility

For the library-wide baseline, see Foundations — Accessibility.

Responsive behavior

For the shared container and viewport rules, see Foundations — Responsive behavior.

Dark mode

For theme activation, token overrides, and contrast guidance, see Foundations — Dark mode.

Attributes

Attribute	Default	Description
name	(blank)	Submitted with the form.
label	(blank)	Floating label.
label-position	default	default keeps the floating label; inside keeps a compact label inside the top of the field.
placeholder	(blank)	Placeholder text.
value	(blank)	Current value (also a property).
rows	3	Height in rows.
required	false	Marks the field required. (boolean)
disabled	false	Disable the field. (boolean)
readonly	false	Read-only field. (boolean)
error-message	(blank)	Message shown when validation fails.
show-error-inline	false	Render the error beneath the field. (boolean)
variant	default	default | minimal (bottom border only, no box)
no-clearing	false	Remove the default bottom margin. (boolean)
mention-triggers	[]	JSON array of trigger characters, e.g. '["@","#","/"]'.

Properties (JS only): mentionData — Record<string, { label, value?, description?, image? }[]>.

Methods: focus(), validate(). Parts: field, textarea, mention-panel.

Looking for a rich-text editor? See @loomidev/text-editor, split out from this component’s former toolbar mode.

Events

Event	Detail	Description
input	—	The text or mention value changed.
change	—	The edited value was committed.
loomi-mention-search	{ trigger, query }	A mention query needs matching items.
loomi-mention-select	{ trigger, item }	A mention item was inserted.

<loomi-textarea
  label="Comment"
  onfocus="this.part.field?.classList.add('ring-2')"
></loomi-textarea>

Like any element, you can attach standard listeners (input, focus, blur) directly, or use the exported field/textarea CSS parts to style focus/blur states from outside the shadow root.

document.querySelector("loomi-textarea").addEventListener("input", (e) => {
  console.log(e.target.value);
});

Full Example

<loomi-textarea
  name="message"
  label="Enter message"
  required
  rows="5"
  show-error-inline
  error-message="A comment is required"
></loomi-textarea>

Framework integration

<loomi-textarea> is a standard custom element, so the browser can use it in plain HTML, Blade, React, Vue, Angular, Svelte, Astro, and most other frameworks. The important beginner rule is: install the package, import it once before the tag is rendered, then write the Loomi tag in your template.

Where to run commands

Run install commands from the app where you want to use this component. That means the folder that contains that app’s package.json. Do not run these install commands from packages/textarea unless you are editing LoomiUI itself.

cd /path/to/your-app
npm install @loomidev/textarea lit

If you are contributing to LoomiUI itself, first move to the top-level components folder. That is where the main package.json for all packages lives, and pnpm --filter ... commands should be run from there:

cd /path/to/your-copy-of-loomiui/components
pnpm --filter @loomidev/textarea build
pnpm --filter @loomidev/textarea typecheck

Choose your framework

Use the CDN version for prototypes, documentation pages, or a quick reproduction. The import map tells the browser where to find Lit, which Loomi components use internally.

<script type="importmap">
  { "imports": { "lit": "https://esm.sh/lit@3.3.3", "lit/": "https://esm.sh/lit@3.3.3/" } }
</script>
<script type="module" src="https://esm.sh/@loomidev/textarea"></script>

<loomi-textarea name="notes" label="Notes" rows="4"></loomi-textarea>

In Vite, Webpack, Parcel, Rollup, or a framework build pipeline, install the package and import it once in your main app JavaScript file. After that, you can use the Loomi tag anywhere in your app.

import "@loomidev/textarea";

Because this is a form-capable component, give it a name when it should submit with a native <form>. Read its value with new FormData(form).get("the-name") just like you would for a built-in input.

Run the install command from your Laravel project root, then import the component in resources/js/app.js. If your project uses Laravel Vite, npm run dev and npm run build should also be run from the Laravel project root.

cd /path/to/your-laravel-app
npm install @loomidev/textarea lit
npm run dev

resources/js/app.js

import "@loomidev/textarea";

<loomi-textarea name="notes" label="Notes" rows="4"></loomi-textarea>

React can render Loomi tags directly. If you are on React 18, or if you need to pass arrays, objects, or functions, use a ref and assign those values after the component mounts.

import "@loomidev/textarea";

export function LoomiExample() {
  return (
    <loomi-textarea name="notes" label="Notes" rows="4"></loomi-textarea>
  );
}

If TypeScript does not recognize the Loomi tag in JSX, add it to your app’s JSX type declarations.

Import the package in the component that uses it, or once in your main Vue file. Vue templates can use Loomi tags directly. For arrays, objects, or functions, pass the value as a JavaScript property instead of as plain text.

<script setup>
import "@loomidev/textarea";
</script>

<template>
  <loomi-textarea name="notes" label="Notes" rows="4"></loomi-textarea>
</template>

If Vue warns that the tag is an unknown component, configure compilerOptions.isCustomElement for tags that start with loomi- in your Vite or Vue config.

Import the package once and tell Angular to allow custom HTML tags with CUSTOM_ELEMENTS_SCHEMA. For NgModule apps, add the schema to the module instead of the standalone component.

app.component.ts

import { CUSTOM_ELEMENTS_SCHEMA, Component } from "@angular/core";
import "@loomidev/textarea";

@Component({
  selector: "app-root",
  standalone: true,
  schemas: [CUSTOM_ELEMENTS_SCHEMA],
  template: `
    <loomi-textarea name="notes" label="Notes" rows="4"></loomi-textarea>
  `,
})
export class AppComponent {}

Svelte can import the package inside a component script. Astro can import it in the frontmatter of the page or layout where the tag appears.

<script>
  import "@loomidev/textarea";
</script>

<loomi-textarea name="notes" label="Notes" rows="4"></loomi-textarea>

---
import "@loomidev/textarea";
---

<loomi-textarea name="notes" label="Notes" rows="4"></loomi-textarea>

Server-side rendering notes

Frameworks such as Next.js, Nuxt, SvelteKit, and Astro sometimes render HTML on the server before browser-only code runs. If your framework complains, move the Loomi import to client-side code. In Next.js, that usually means a component with "use client"; in Nuxt, it often means a .client.ts plugin.

Dependencies

• @loomidev/core
• @loomidev/theme