Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/pkovzz/ngx-otp-input
One time password input library for Angular
https://github.com/pkovzz/ngx-otp-input
angular input javascript one-time-password otp typescript web
Last synced: 8 days ago
JSON representation
One time password input library for Angular
- Host: GitHub
- URL: https://github.com/pkovzz/ngx-otp-input
- Owner: pkovzz
- License: mit
- Created: 2021-02-20T14:53:32.000Z (almost 4 years ago)
- Default Branch: master
- Last Pushed: 2025-01-22T14:51:50.000Z (16 days ago)
- Last Synced: 2025-01-22T15:13:51.943Z (16 days ago)
- Topics: angular, input, javascript, one-time-password, otp, typescript, web
- Language: TypeScript
- Homepage: https://ngx-otp-input.vercel.app/
- Size: 987 KB
- Stars: 26
- Watchers: 1
- Forks: 13
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
- trackawesomelist - ngx-otp-input (⭐24) - One time password input library for Angular. (Recently Updated / [Oct 03, 2024](/content/2024/10/03/README.md))
- awesome-angular - ngx-otp-input - One time password input library for Angular. (Table of contents / Third Party Components)
- fucking-awesome-angular - ngx-otp-input - One time password input library for Angular. (Table of contents / Third Party Components)
README
# ngx-otp-input
[](./LICENSE.txt)
:warning: **Important note:** starting with version 1.0.0, the library has been completely rewritten to use standalone components and introduce breaking changes. As the section "Requirements" states, the library now requires Angular 14 or above.
## What is this?
This is a simple Angular library that allows you to create an OTP (One Time Password) form by providing a set of options. The library is designed to be easy to use and highly customizable, allowing you to configure the form to suit your needs. If you like the library, please consider giving it a star on GitHub.
### Demo page
http://ngx-otp-input.vercel.app
## Requirements
To use this library, your project must be running **Angular 14** or above. This requirement stems from our adoption of standalone components, which are an integral feature in Angular's modern development approach. Standalone components offer a more streamlined and modular way to manage your components and simplify the dependency management, positioning them as the future of Angular development.
## Installation
To install this library, run:
```bash
npm install ngx-otp-input --save
```
## Example Usage
Since the library uses standalone components, you can directly import and use them in your Angular application without needing to declare them in any module. For more configuration options, refer to the [Configuration options](#configuration-options) section.
```typescript
import { Component } from '@angular/core';
import { NgxOtpInputComponent, NgxOtpInputComponentOptions } from 'ngx-otp-input';
@Component({
selector: 'app-root',
standalone: true,
imports: [NgxOtpInputComponent],
template: `
Welcome to My Angular App
`,
styleUrls: ['./app.component.scss'],
})
export class AppComponent {
otpOptions: NgxOtpInputComponentOptions = {...};
}
```
## Inputs
### `options: NgxOtpInputComponentOptions`
The `options` input is an object that allows you to configure the OTP form. For a list of available options, refer to the [Configuration options](#configuration-options) section.
### `otp: string | null | undefined`
The `otp` input is a string that allows you to set the OTP value of the form. This input is useful when you want to pre-fill the form with an OTP value. If the `otp` input is set to `null` or `undefined`, the form will be empty. The library will match the length of the OTP value with the `otpLength` option and fill the input fields accordingly, in case the OTP value is shorter than the `otpLength` option, the remaining fields will be empty. If the given value will not match the `regexp` option, the library will throw an error.
### `status: NgxOtpStatus | null | undefined`
The `status` input is a string that allows you to set the status of the OTP form. The status can be one of the following values: `null`, `undefined`, `'success'` or `'failed'`. This status is only used to visually indicate the result of the OTP verification process.
For type safety, you can use the `NgxOtpStatus` enum:
```typescript
import { NgxOtpStatus } from 'ngx-otp-input';
@Component({
selector: 'app-root',
standalone: true,
imports: [NgxOtpInputComponent],
template: ` `,
})
export class AppComponent {
status = NgxOtpStatus;
}
```
### `disabled: boolean`
The `disabled` input is a boolean that allows you to disable the OTP form. When set to `true`, the form will be disabled and the user will not be able to interact with it.
## Outputs
### `otpChange: string[]`
The `otpChange` output is an event that is emitted whenever the OTP value changes. The event payload is an array of strings, where each string represents a value in the OTP form.
### `otpComplete: string`
The `otpComplete` output is an event that is emitted whenever the OTP form is completed. The event payload is string, which represents the complete OTP value.
## Configuration options
The `NgxOtpInputComponentOptions` interface allows you to configure the OTP form. The following options are available:
| Option | Type | Default value | Description |
| -------------------- | -------- | ------------: | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `otpLength` | number | 6 | The number of inputs in the OTP form |
| `autoFocus` | boolean | true | Whether the first input should be focused automatically |
| `autoBlur` | boolean | true | Whether the form should be blurred on complete |
| `hideInputValues` | boolean | false | Whether the input values should be shown as password fields |
| `regexp` | RegExp | /^[0-9]+$/ | The regular expression that the input values should match |
| `showBlinkingCursor` | boolean | true | Whether the input fields should have a blinking cursor |
| `ariaLabels` | string[] | [] | An array of strings that represent the aria-labels for each input field. For more information, please refer to the [More on aria-labels](#more-on-aria-labels) section. |
| `inputMode` | string | 'numeric' | The `inputmode` attribute of the input fields. For more information, please refer to the [HTML `inputmode` attribute](#html-inputmode-attribute) section. |
## Styling
The library provides a set of CSS classes that you can use to style the OTP form. The following classes are available:
| Class name | Description |
| ------------------------ | -------------------------------------- |
| `ngx-otp-input-form` | The main container of the OTP form |
| `ngx-otp-input-box` | The input field of the OTP form |
| `ngx-blinking-cursor` | The blinking cursor of the input field |
| `ngx-otp-input-disabled` | The disabled state of the form |
| `ngx-otp-input-filled` | The filled state of an input field |
| `ngx-otp-input-success` | The success state of the form |
| `nngx-otp-input-failed` | The failed state of the form |
### How to use the classes
Styling is quite simple, but you have to use the classes directly in **root** style file, otherwise it will not work:
```scss
ngx-otp-input {
.ngx-otp-input-form {
...
}
.ngx-otp-input-box {
...
}
...
}
```
## Reset the form
In order to reset the form, you can use the `reset` method of the `NgxOtpInputComponent`:
First, get a reference to the component in your template:
```html
```
Then, get a reference to the component in your component class:
```typescript
import { Component, ViewChild } from '@angular/core';
import { NgxOtpInputComponent } from 'ngx-otp-input';
@Component({
selector: 'app-root',
standalone: true,
imports: [NgxOtpInputComponent],
template: `
`,
})
export class AppComponent {
@ViewChild('otpInput') otpInput: NgxOtpInputComponent;
resetForm() {
this.otpInput.reset();
}
}
```
Under the hood, the `reset` method will clear all the input values and reset the form to its initial state. For more information, refer to the [Angular FormArray reset](https://angular.dev/api/forms/FormArray#reset) documentation.
## More on aria-labels
The `ariaLabels` option allows you to provide a set of strings that represent the aria-labels for each input field. This option is useful for making the form more accessible to users who rely on screen readers. The `aria-label` attribute provides a way to specify a string that labels the current element, which can be read by screen readers to provide additional context to the user. The library will automatically assign the `aria-label` attribute to each input with a default value of `One Time Password Input Number` followed by the input index. However, you can override this default value by providing your own set of labels in the `ariaLabels` option.
If you provide an array of strings in the `ariaLabels` option, the library will use the values in the array to assign the `aria-label` attribute to each input field. The array should contain the same number of strings as the `otpLength` option, with each string representing the label for the corresponding input field. If the array contains fewer strings than the `otpLength` option, the library will use the default value for the remaining input fields.
## HTML `inputmode` attribute
The `inputMode` option allows you to set the `inputmode` attribute of the input fields. The `inputmode` attribute provides a hint to the browser about the type of data that is expected to be entered by the user. This hint can help the browser provide a more appropriate **virtual keyboard** layout for the input field, making it easier for the user to enter the correct data. The `inputMode` option accepts a string value that represents the input mode of the input fields. For more details, check out this [documentation](https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/inputmode).
Please note, that `regexp` option should be set to support the `inputmode` attribute. For example, if you set the `inputMode` option to `text` and the `regexp` option to `/^[a-zA-Z]+$/`, the browser will provide a virtual keyboard layout that is optimized for entering text data, but if the `inputMode` option is set to `numeric` and the `regexp` is still `/^[a-zA-Z]+$/`, the browser may provide a numeric keyboard layout, which may not be suitable for entering text data.
**Default** options for `inputMode` and `regexp` are set to `'numeric'` and `/^[0-9]+$/` respectively, as these are the most common values for one time password inputs.
## Side notes
If `hideInputValues` is set to `true`, the input values will be hidden by default, using the `password` input type. However certain password managers may place their browser extension icon on the input field, which may interfere with the input field's appearance.
## Contributing
If you would like to contribute to this project, please refer to the [CONTRIBUTING](CONTRIBUTING.md) file for more information.
## Code of Conduct
Please read the [CODE OF CONDUCT](CODE_OF_CONDUCT.md) file for more information.
## Changelog
See the [CHANGELOG](CHANGELOG.md) file for details.
## License
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
_This project is tested with BrowserStack_