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

audit-debounce

v0.1.1

Published

rxjs operator to debounce and audit simultaenously

Downloads

69

Readme

npm package minimized gzipped size npm GitHub Workflow Status

audit-debounce

RxJS operator to debounce and audit simultaenously. When you debounce() a particularly active observable, you might have to wait a long time to get any value from it (if it is constantly emitting values). auditDebounce() solves this problem by debouncing the observable, but also emitting the latest value after a given duration has passed.

import { auditDebounceTime } from 'audit-debounce'

source$.pipe(
  // debounce for 100ms, but also emit the latest value after 1000ms
  auditDebounceTime(100, 1000)
)
import { timer } from 'rxjs'
import { auditDebounce } from 'audit-debounce'

source$.pipe(
  // debounce for 100ms, but also emit the latest value after 1000ms
  auditDebounce(
    () => timer(100),
    () => timer(1000)
  )
)

Contents

Installation

Node:

npm i audit-debounce

Browser / Deno:

import { auditDebounceTime } from 'https://esm.sh/audit-debounce'

Usage

This package provides the following functions:

function auditDebounceTime<T>(
  debounceTime: number,
  auditTime: number,
  scheduler?: SchedulerLike
): MonoTypeOperatorFunction<T>
function auditDebounce<T>(
  debounceSelector: (value: T | typeof CANCEL_SIGNAL) => ObservableInput<any>,
  auditSelector: (value: T | typeof CANCEL_SIGNAL) => ObservableInput<any>
): MonoTypeOperatorFunction<T>

The operator will debounce incoming values, but also makes sure values are emitted after certain duration is passed.

source$:           --a-b------c-d-e-f------h-i-j-k-l----->
debounceSelector$:   -----x   ---------x   -----------x
auditSelector$:      -------y -------y     -------y
result$:           -------b----------f------------k---l-->

Contribution

You need node, NPM to start and git to start.

# clone the code
git clone [email protected]:loreanvictor/audit-debounce.git
# install stuff
npm i

Make sure all checks are successful on your PRs. This includes all tests passing, high code coverage, correct typings and abiding all the linting rules. The code is typed with TypeScript, Jest is used for testing and coverage reports, ESLint and TypeScript ESLint are used for linting. Subsequently, IDE integrations for TypeScript and ESLint would make your life much easier (for example, VSCode supports TypeScript out of the box and has this nice ESLint plugin), but you could also use the following commands:

# run tests
npm test
# check code coverage
npm run coverage
# run linter
npm run lint
# run type checker
npm run typecheck