Required If Web Component

Currently, HTML only supports making a field required or optional. Sometimes you need a field to be required only when certain other fields have a (particular) value. The form-required-if web component enables that.

TypeScript & Framework Support

• Ships with .d.ts definitions so editors and TypeScript builds get full type information for FormRequiredIfElement.
• conditions, indicator, and indicator-position now reflect between properties and attributes, keeping frameworks in sync with DOM state.
• _upgradeProperty ensures properties set before the element is defined are captured and reflected once connected.

Demos

• Comprehensive Demo (Source)
• ESM.sh CDN Demo (Source)
• unpkg CDN Demo (Source)

Installation

npm install @aarongustafson/form-required-if

Usage

Option 1: Import the class and define manually

Import the class and define the custom element with your preferred tag name:

import { FormRequiredIfElement } from '@aarongustafson/form-required-if';

// Define with default name
customElements.define('form-required-if', FormRequiredIfElement);

// Or define with a custom name
customElements.define('my-conditional-required', FormRequiredIfElement);

Option 2: Auto-define the custom element (browser environments only)

Use the guarded definition helper to register the element when customElements is available:

import '@aarongustafson/form-required-if/define.js';

If you prefer to control when the element is registered, call the helper directly:

import { defineFormRequiredIf } from '@aarongustafson/form-required-if/define.js';

defineFormRequiredIf();

You can also include the guarded script from HTML:

<script src="./node_modules/@aarongustafson/form-required-if/define.js" type="module"></script>

CDN Usage

You can also use the component directly from a CDN:

<script src="https://unpkg.com/@aarongustafson/form-required-if@latest/define.js" type="module"></script>

API

Markup Assumptions

This web component assumes the fields you reference in conditions exist in the DOM when the component is loaded. If they don’t, they will be ignored.

Implementation notes

1. Field markup changes. When the field is in its required state, it will receive both the required and aria-required="true" attributes.
2. Required indicator. If you include a indicator, it will be injected into the label at the appropriate position (before or after the label text). If your indicator is HTML, that is what will be inserted. When the value is just text, it will be injected inside a span. In either case, the root element of the indicator will be set to both hidden and aria-hidden="true" while the field is not required. Those will be removed when the field is in its required state.

Examples

Basic Usage

<form>
  <label for="email">Email</label>
  <input type="email" id="email" name="email">

  <form-required-if conditions="email=*" indicator="*">
    <label for="phone">Phone (required if email provided)</label>
    <input type="tel" id="phone" name="phone">
  </form-required-if>

  <button type="submit">Submit</button>
</form>

Multiple Conditions (OR logic)

<form-required-if conditions="email=*||phone=*" indicator="<b>*</b>">
  <label for="name">Name (required if email OR phone provided)</label>
  <input type="text" id="name" name="name">
</form-required-if>

Specific Value Conditions

<form-required-if conditions="contact-method=email" indicator="*">
  <label for="email">Email Address</label>
  <input type="email" id="email" name="email">
</form-required-if>

Checkbox Conditions

<form-required-if conditions="newsletter=yes" indicator="*">
  <label for="email">Email (required for newsletter)</label>
  <input type="email" id="email" name="email">
</form-required-if>

Custom Indicator Positioning

<form-required-if conditions="email=*" indicator="*" indicator-position="before">
  <label for="phone">Phone</label>
  <input type="tel" id="phone" name="phone">
</form-required-if>

Browser Support

This web component works in all modern browsers that support:

• Custom Elements v1
• ES Modules (for module usage)

For older browsers, you may need polyfills for Custom Elements.

Development

Testing

# Run tests
npm test

# Run tests once
npm run test:run

# Run tests with UI
npm run test:ui

# Run tests with coverage
npm run test:coverage

Linting and Formatting

# Lint code
npm run lint

# Format code
npm run format