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

@filter-enginez/eslint

v0.0.4

Published

ESLint rules and flat-config presets for Filter EngineZ projects: keep isomorphic code free of browser APIs and the Redux mirror read-only.

Readme

@filter-enginez/eslint

ESLint rules and shared flat-config presets for Filter EngineZ projects. Two sub-exports:

  • @filter-enginez/eslint/plugin — the plugin: three rules plus the recommended and strict presets.
  • @filter-enginez/eslint/config — the shared flat configs this repository lints itself with: base, react and nodeIsomorphic.

Install

pnpm add @filter-enginez/eslint

Peer dependencies: eslint@^10.0.0 — supplied by your app.

Usage

Import the plugin's default export (import filterEnginez from '@filter-enginez/eslint/plugin') and add filterEnginez.configs.recommended — or filterEnginez.configs.strict — to the array your eslint.config.js exports. The plugin registers under the @filter-enginez prefix, so a rule is configured as '@filter-enginez/no-browser-api-in-core'.

| Preset | Rules | | ------------- | --------------------------------------------------------------------------- | | recommended | no-direct-mirror-mutation (error) | | strict | no-direct-mirror-mutation (error), filter-rule-naming-convention (warn) |

no-browser-api-in-core is in neither preset, because which files must stay isomorphic is a per-project decision. Enable it for those files yourself, or use the nodeIsomorphic config from @filter-enginez/eslint/config, which turns it on.

Rules

no-browser-api-in-core

Reports references to browser-only globals (window, document, localStorage, sessionStorage, history, navigator, XMLHttpRequest, DOM element and event classes, and the rest of DEFAULT_FORBIDDEN_GLOBALS) in code that must run in any JavaScript runtime. Globals every runtime provides, such as URL, are allowed, and a local binding that shadows a global name is not reported. Options:

  • extraGlobals — names to forbid in addition to the defaults.
  • allowedSubpaths — globs of files that are browser-only by design and skipped; defaults to **/storage/browser/**, **/browser/** and **/keyboard/** (exported as DEFAULT_NO_BROWSER_API_ALLOWED_SUBPATHS).

no-direct-mirror-mutation

The @filter-enginez/redux-bridge mirror is written only by the bridge. This rule reports any other code that could write it: importing stateUpdated, accessing *.actions.stateUpdated, dispatching a { type: '<slice>/stateUpdated' } literal, or declaring a stateUpdated reducer in createSlice. Change the engine instead (addRule, setExpression, setSourceData, …) and let the bridge mirror it. Options:

  • sliceNames — the mirror slice names to match in action-type strings; default ['filters'].
  • allowedSubpaths — globs of files that may write the mirror (the bridge itself).

filter-rule-naming-convention

For classes whose direct superclass is FilterRule (or BaseFilterRule / AbstractFilterRule): the class name ends in Rule, and the file lives under a rules directory. Options: requireRuleSuffix (default true), requireRulesDirectory (default true) and rulesDirectoryGlob (default **/rules/**).

Documentation

Consumer guides live in the engine repository under docs/guides/:

  • extending_rules.md — writing a custom FilterRule that survives serialization
  • json_config.md — declaring filters as data, and why the format is safe to accept from a tenant
  • acceleration_tuning.md — what the five acceleration toggles are worth, measured
  • worker_offload.md — running the engine in a Web Worker

Project home, with six live demos: https://filterenginez.com. Documentation site: https://docs.filterenginez.com.

Apache-2.0. See LICENSE.md and NOTICE.md, both included in this package.