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

@qrvey/filters

v0.1.1

Published

Helpers and logic for Filtering Data in Qrvey app

Downloads

1,558

Readme

@qrvey/filters 0.1.1

Helpers and logic for Filtering Data in Qrvey app

Release pipelines

Recommended consumption guide

This package exposes ESM + CommonJS:

  • import (ESM) for modern bundlers and better tree shaking.
  • require (CommonJS) for legacy implementations.

1) Recommended (ESM with tree shaking)

Use named imports from the entrypoint or specific subpaths.

// Good: allows bundlers to remove unused exports
import { FilterManager, FilterBuilder } from "@qrvey/filters";

// Better for critical bundles: import only the module you need
import { FilterManager } from "@qrvey/filters/classes/index";

2) Avoid for optimized bundles

// Avoid in frontend apps: can pull more code into the bundle
import * as QrveyFilters from "@qrvey/filters";

3) CommonJS compatibility

For Node projects or integrations that require CommonJS:

const { FilterManager } = require("@qrvey/filters");
const { FilterManager } = require("@qrvey/filters/classes/index");

4) Recommendations for consumer apps

  • Prefer import over require in frontend code.
  • Use subpaths (@qrvey/filters/<module>) on performance-critical paths.
  • Keep tree shaking enabled in your bundler (Webpack/Rollup/Vite in production mode).

Modules

| Module | Description | Subpath import | API docs | | ------ | ----------- | -------------- | -------- | | classes | Core classes: FilterBuilder, FilterManager, FilterAdapter, FilterSearcher, FilterValidation, FilterValues and FilterResources. | @qrvey/filters/classes/index | docs | | helpers | Stateless utility functions for filter adaptation, settings, ID generation, type resolution and condition handling. | @qrvey/filters/helpers/index | docs | | models | TypeScript interfaces and types for FilterBuilder, FilterResources and FilterSearcher internals. | @qrvey/filters/models/index | docs | | resources | Enums, constants and panel interfaces for filter functions, grouping, logic, operators, scopes, validators, values, visual options and the DEFAULT_FILTER. | @qrvey/filters/resources/index | docs |