npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

ngx-form-stepper

v0.0.12

Published

[🇫🇷 Lire la version française](https://github.com/rayaneriahi/ngx-form-stepper/blob/main/README.fr.md)

Readme

ngx-form-stepper

🇫🇷 Lire la version française

ngx-form-stepper is an Angular library that allows you to create multi-step forms with field-level validation, extremely strongly typed.

It prevents creating invalid states at development time, not at runtime.

Intended for Angular developers who want robust, typed, and maintainable forms without complex configuration.

Why?

  • Simple multi-step forms declaration
  • Quick per-field validation setup
  • Impossible to associate a wrong validator to an Input
  • Values always consistent with their type
  • Unique return keys required
  • No as const needed

Installation

npm install ngx-form-stepper

Feedback and suggestions are very welcome.

Please feel free to open an issue or a discussion. Any feedback helps improve the library.

Quick example

step1 = new Step([
  new Input(InputType.Text, null, 'firstName', 'First name', [required('First name is required')]),
  new Input(InputType.Text, null, 'lastName', 'Last name', [required('Last name is required')]),
]);

step2 = new Step([
  new Input(InputType.Email, null, 'email', 'E-mail', [
    required('E-mail is required'),
    email('E-mail is invalid'),
  ]),
  new Input(InputType.Password, null, 'password', 'Password', [
    required('Password is required'),
    strongPassword('Password is too weak'),
  ]),
]);

signupForm = new FormStepper([step1, step2], {
  title: 'Sign in',
  buttonText: { next: 'Next', previous: 'Previous', final: 'Sign up' },
});

onComplete() {
  console.log(signupForm.values);
}
<app-form-stepper [formStepper]="signupForm" (completed)="onComplete()" />

Input

export class Input<
  T extends InputType,
  D extends InputDefaultValue<T>,
  K extends string,
  V extends ValidatorTuple<ValidatorsNamesOfType<T>>
> {
  readonly defaultValue: D;

  constructor(
    readonly type: T,
    defaultValue: D,
    readonly returnKey: IsCamelCase<K> extends true ? K : never,
    readonly label: string,
    readonly validators?: HasDuplicateValidators<V> extends true ? never : V
  ) {
    this.defaultValue = (
      type === InputType.Checkbox ? (defaultValue === null ? false : defaultValue) : defaultValue
    ) as D;
  }
}

export enum InputType {
  Text = 'text',
  Password = 'password',
  Email = 'email',
  Number = 'number',
  Tel = 'tel',
  Checkbox = 'checkbox',
  Date = 'date',
  Select = 'select',
}

Each Input type only accepts compatible default values.

export type InputDefaultValue<T extends InputType> = T extends InputType.Text
  ? string | null
  : T extends InputType.Password
  ? string | null
  : T extends InputType.Email
  ? string | null
  : T extends InputType.Number
  ? number | null
  : T extends InputType.Tel
  ? string | null
  : T extends InputType.Checkbox
  ? boolean | null
  : T extends InputType.Date
  ? Date | null
  : T extends InputType.Select
  ? Select<SelectItemTuple, number | null>
  : never;

Validator

A validator is a function that can be passed to an Input. It takes different arguments like conditional values or error text.

export function minLength(min: number, errorText: string): Validator<'minLength'> {
  const name: StandardValidatorNameFn<'minLength'> = (params: { key: string }) =>
    `${params.key}-minLength`;

  const fn = (params: { key: string }) => (control: AbstractControl<string>) => {
    const customName: StandardValidatorName<'minLength'> = `${params.key}-minLength`;

    return control.value.length < min ? { [customName]: true } : null;
  };

  return {
    kind: 'minLength',
    name,
    fn,
    errorText,
  };
}

export type ValidatorsNames =
  | 'required'
  | 'check'
  | 'confirm'
  | 'minLength'
  | 'maxLength'
  | 'min'
  | 'max'
  | 'integer'
  | 'pattern'
  | 'strongPassword'
  | 'email'
  | 'phone'
  | 'minDate'
  | 'maxDate';

Each Input type only accepts compatible validators.

export type ValidatorsNamesOfType<T extends InputType> = T extends InputType.Text
  ? 'required' | 'confirm' | 'minLength' | 'maxLength' | 'pattern'
  : T extends InputType.Password
  ? 'required' | 'confirm' | 'strongPassword' | 'pattern'
  : T extends InputType.Email
  ? 'required' | 'confirm' | 'email'
  : T extends InputType.Number
  ? 'required' | 'confirm' | 'min' | 'max' | 'integer'
  : T extends InputType.Tel
  ? 'required' | 'confirm' | 'phone'
  : T extends InputType.Checkbox
  ? 'check'
  : T extends InputType.Date
  ? 'required' | 'confirm' | 'minDate' | 'maxDate'
  : T extends InputType.Select
  ? 'required'
  : never;

Reusing typed validators

ngx-form-stepper allows you to factor them out, then create groups of validators that are compatible only with a given Input type:

reqVal: Validator<'required'> = required('Field is required');

emailValidators: ValidatorTuple<ValidatorsNamesOfType<InputType.Email>> = [
  reqVal,
  email('E-mail is not valid'),
];

What is impossible (and intentional)

// ❌ Compilation error
const badValidators: ValidatorTuple<ValidatorsNamesOfType<InputType.Number>> = [
  email('Invalid email'),
];

This error is detected at compile time, even before running the application.

Select

Tuple of one or more SelectItem.

currentIndex must be a valid index of the tuple or null.

select = new Input(
  InputType.Select,
  new Select(
    [
      { label: 'Male', value: 'male' },
      { label: 'Female', value: 'female' },
    ],
    0
  ),
  'gender',
  'Gender'
);

export class Select<T extends SelectItemTuple, I extends number | null> {
  current: SelectItem | null;

  constructor(readonly items: T, readonly currentIndex: HasIndex<T, I> extends true ? I : never) {
    this.current = currentIndex === null ? null : this.items[currentIndex];
  }
}

export type SelectItem = {
  label: string;
  value: string;
};

Assigning an invalid currentIndex is impossible.

// ❌ Compilation error
invalid = new Input(
  InputType.Select,
  new Select(
    [
      { label: 'Male', value: 'male' },
      { label: 'Female', value: 'female' },
    ],
    5
  ),
  'gender',
  'Gender'
);

Step

Tuple of one or more Inputs.

export class Step<T extends InputTuple> {
  constructor(
    readonly inputs: HasDuplicateReturnKeys<T> extends true ? never : T,
    readonly config?: StepConfig
  ) {}
}

export type StepConfig = Readonly<{
  title: string;
}>;

Duplication of returnKey is forbidden (and intentional)

// ❌ Compilation error
new Step([
  new Input(InputType.Text, null, 'name', 'First name'),
  new Input(InputType.Text, null, 'name', 'Last name'),
]);

FormStepper

Impossible to duplicate an Input return key between two Steps.

Tuple of one or more Steps.

export class FormStepper<T extends StepTuple> {
  readonly values: FormStepperValues<T>;

  constructor(
    readonly steps: HasDuplicateReturnKeys<T> extends true ? never : T,
    readonly config: T extends MultiStepTuple ? MultiStepConfig : SingleStepConfig
  ) {
    this.values = Object.fromEntries(
      steps.flatMap((step) => step.inputs.map((input) => [input.returnKey, input.defaultValue]))
    ) as FormStepperValues<T>;
  }
}

Configuration object depending on the number of Steps.

export type SingleStepConfig = Readonly<{
  title?: string;
  actionText?: RedirectItem[];
  buttonText: SingleStepButtonText;
  footerText?: RedirectItem[];
  classNames?: SingleStepClassNames;
}>;

export type MultiStepConfig = Readonly<{
  title?: string;
  actionText?: RedirectItem[];
  buttonText: MultiStepButtonText;
  footerText?: RedirectItem[];
  classNames?: MultiStepClassNames;
}>;

RedirectItem[]

A RedirectItem[] is an array of strings or RedirectUrl objects, a kind of mini TS language to create texts with clickable links.

actionText = ['You already have an account?', { url: '/signin', urlText: 'Sign in' }];

export type RedirectUrl = Readonly<{ url: string; urlText: string }>;

export type RedirectText = string;

export type RedirectItem = RedirectText | RedirectUrl;

ButtonText

buttonText property of FormStepper depends on the number of Steps.

export type SingleStepButtonText = string;

export type MultiStepButtonText = Readonly<{
  final: string;
  previous: string;
  next: string;
}>;

ClassNames

To add your own styles to a FormStepper, I recommend creating a separate style file and adding your classes there. You should then import the created file into the global styles file of your app.

classNames: SingleStepClassNames = {
  title: 'fs-title',
  input: {
    error: 'fs-input-error',
  },
};

form = new FormStepper([this.step], {
  buttonText: 'Submit',
  classNames: this.classNames,
});
/* app/fs.css */

.fs-title {
  color: blue;
}

.fs-input-error {
  color: red;
}
/* styles.css */

@import 'app/fs.css';

classNames property of FormStepper also depends on the number of Steps.

export type SingleStepClassNames = DeepPartial<{
  container: string;
  title: string;
  actionText: {
    container: string;
    text: string;
    url: string;
  };
  step: {
    container: string;
    title: string;
    form: string;
    inputContainer: string;
  };
  input: {
    container: string;
    label: string;
    required: string;
    input: string;
    errorContainer: string;
    error: string;
  };
  button: {
    container: string;
    button: string;
    disabled: string;
  };
  footerText: {
    container: string;
    text: string;
    url: string;
  };
}>;

export type MultiStepClassNames = DeepPartial<{
  container: string;
  title: string;
  actionText: {
    container: string;
    text: string;
    url: string;
  };
  step: {
    container: string;
    title: string;
    form: string;
    inputContainer: string;
  };
  input: {
    container: string;
    label: string;
    required: string;
    input: string;
    errorContainer: string;
    error: string;
  };
  button: {
    container: string;
    button: string;
    disabled: string;
    first: string;
    final: string;
    previous: string;
    next: string;
  };
  footerText: {
    container: string;
    text: string;
    url: string;
  };
}>;

In summary

  • Common errors are impossible
  • Types guide the implementation
  • The final form is always consistent
  • The compiler becomes an ally