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

@slaviczavik/stream-search

v1.5.0

Published

Event based module for searching streams.

Downloads

2

Readme

Build Status

Description

Node.js event based module for searching streams using the Boyer–Moore–Horspool algorithm.

Requirements

Node.js 6.14.3 or higher is required.

Installation

npm i @slaviczavik/stream-search

Example

Code

const StreamSearch = require('@slaviczavik/stream-search')
const search = StreamSearch('AQD')

search.on('part', function (obj) {
  const isMatch = obj['isMatch']
  const start = obj['start']
  const end = obj['end']
  const data = obj['data']

  if (isMatch) {
    console.log(`Found! [${start} - ${end}]`)
  }
  else {
    console.log(`Not found!`)
  }

  if (data) {
    console.log(data.toString('ascii'))
  }
})

search.add('--AQD-QDD-DQD--')
search.end()

Output

> Found! [2 - 4]
> --AQD
> Not found!
> -QDD-DQD--

API

Constructor

StreamSearch(needle, limit)

| Name | Required | Type | Description | Default | - | - | - | - | - | | needle | true | string, buffer | The needle what we are searching for. | none | | limit | false | integer | The maximum number of matches. | Infinity |

Number of matches is reseted after the end method calling.

Methods

add(haystack)

Call this method every time you receive a new stream data. If there were some unprocessed data in the previous request, this data will be processed with this new data.

| Parameter | Required | Type | Description | - | - | - | - | | haystack | true | string, buffer | Your data you want to search. |

end()

Calling this method you signals that no more data will be passed. If there are some trailing data (too few to run the algorithm), this data will be emitted back to user.

Events

part(object)

Emitted every time a match was or was not made. In both case, a processed chunk of data is available. If match was made, the needle is between start (inclusive) and end (inclusive).

The object contains following properties:

| Property | Type | Description | - | - | - | | isMatch | boolean | Bool value that data contains the needle. | | data | buffer | Returned data from the haystack. | | start | integer, undefined | Start position of needle (if any) in the haystack (inclusive). | | end | integer, undefined | End position of needle (if any) in the haystack (inclusive). |

The property end also indicates the end of the data.