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

postkit-search-library

v1.0.12

Published

Search post content. ## Exports

Readme

Post Search

Purpose

Search post content.

Exports

buildSearchableText(post: Post): string

  • Description: combines the searchable fields (title, body, author, tags, category) into a single string for matching

matchesQuery(post: Post, query: string): boolean

  • Description: returns whether a post matches the query. Matching is case-insensitive and fuzzy — query tokens are compared against post tokens, so minor typos and partial matches are tolerated

searchPosts(posts: Post[], query: string): Post[]

  • Description: filters the array to only posts that match the query. Uses matchesQuery internally — the returned posts are those for which matchesQuery returns true

Example Usage

export type PostStatus = 'draft' | 'review' | 'published'

export type Post = {
  id: string
  title: string
  body: string
  author: string
  tags: string[]
  category: string
  status: PostStatus
  createdAt: string
  updatedAt: string
}

const postArray: Post[] = [...];
const query = "hot dog";

// buildSearchableText example — searches title, body, author, tags, and category
const searchableText = buildSearchableText(post);

// searchPosts example
const searchReturnArray = searchPosts(postArray, query);

// matchesQuery example
const firstPost = searchReturnArray[0];
const queryMatches = matchesQuery(firstPost, query);

Edge Cases

Malformed input items

If the input array contains items that do not conform to the Post type, searchPosts should ignore those items or handle them safely without crashing.

Empty query string

If the query is an empty string (""), searchPosts returns all posts in the array, since every post trivially matches an empty search.

Design Notes

Search is case-insensitive and whitespace normalized via .toLowerCase() and .trim(). Post fields are tokenized into individual words for matching.