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 🙏

© 2024 – Pkg Stats / Ryan Hefner

ngx-input-search

v3.0.8

Published

Angular directive to put in your search inputs. With its only output you will be able to get what the user writes with all good practices related to search input

Downloads

192

Readme

ngx-input-search

npm version NPM Licence

CircleCI

dependencies Status devDependencies Status

coverage reliability rating security rating scale rating

Quality Gate Sonar Cloud

TL;DR:

Angular directive to put in your search inputs to improve the User Experience (UX). With its only output you will be able to get what the user writes with good practices related to search inputs such as:

  • Wait until the user stops writing to perform the desired action
  • Avoid performing the action over the same stream
  • Trim the white-spaces on the criteria
  • Stream when the criteria's length is greater than the desired
<input type="text" (ngxInputSearch)="doTheSearch($event)"/>

How to use it

dummy.component.ts

@Component({
  selector: 'dummy-component',
  templateUrl: 'dummy.component.html',
})
class DummyComponent {

  doTheSearch($event: Event) {
    const stringEmitted = ($event.target as HTMLInputElement).value;
    console.log(stringEmitted);
  }
}

dummy.component.html

<label for="search-box"> Search Input </label>
<input id="search-box" type="text" (ngxInputSearch)="doTheSearch($event)"/>

<br>

<span> The search box triggers -> {{ stringEmitted }} </span>

Demo

  • online demo: https://bikecoders.github.io/ngx-input-search/
  • demo-app: Source code available

Getting started

  1. Install ngx-input-search:
# using npm
npm install ngx-input-search --save

# using yarn <3
yarn add ngx-input-search
  1. Import the installed library:
import { InputSearchModule } from 'ngx-input-search';

@NgModule({
  ...
  imports: [
    ...
    InputSearchModule
  ]
})
export class AppModule { }
  1. Use it in your component
@Component({
  selector: 'dummy-component',
  template: `
    <input type="text" (ngxInputSearch)="doTheSearch($event)"/>
  `,
})
class DummyComponent {
  doTheSearch($event: Event) {
    const stringEmitted = ($event.target as HTMLInputElement).value;
    // Your request...
  }
}

Properties

| Name | Description | | :----------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------- | | @Output() ngxInputSearch: EventEmitted<Event> | Event emitted when the user has entered the search criteria in the input element. | | @Input() debounceTime: number = 400 | Indicates how much time in ms it will wait for the users stops typing. By default is 400ms. | | @Input() stringLength: number = 0 | Indicates the minimum length that must have the string to be emitted. By default is 0. | | @Output() stringTooShort: EventEmitted<string> | Event emitted when the string written length is shorter than the minimum defined by the input property stringLength. The event contains the current criteria. | | @Output() emptyInput: EventEmitted<void> | Event emitted when the input is empty. |

Why?

When we want to implement a search input we usually want to wait until the user stops writing to make the request and also check if the search criteria is different than the last one to avoid making the same request right away.

With this directive we have the desired behavior.