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

@x-filter/react

v0.2.0

Published

Headless React hooks for the X-Filter query builder — state management, view models, DSL editor, URL sync, presets, undo/redo, and keyboard navigation.

Readme

@x-filter/react

Headless React layer for @x-filter/core. This package owns React state, view-model shaping, DSL editor state, and adapter contracts without rendering a specific UI kit.

Install

pnpm add @x-filter/react @x-filter/core react react-dom

Concepts

  • useFilterBuilder manages controlled or uncontrolled Filter state and wraps core mutations such as addRule, updateRule, addGroup, and moveRule.
  • useFilterViewModel turns a core Filter plus FieldSchema[] into UI-ready rule/group nodes with resolved field metadata, operator metadata, validation errors, and ARIA labels.
  • useDslEditor keeps a formatted DSL draft in sync with the current filter, exposes completions, parses on commit, and reports parse errors.
  • useReorderContract exposes adapter-friendly reorder handlers used by DnD implementations.

Minimal Builder

import type { FieldSchema } from '@x-filter/core';
import { formatDSL } from '@x-filter/core';
import { useFilterBuilder, useFilterViewModel } from '@x-filter/react';

const schema: FieldSchema[] = [
  {
    name: 'status',
    label: 'Status',
    type: 'select',
    defaultOperator: 'equals',
    defaultValue: 'open',
    operators: [{ name: 'equals', label: 'equals', arity: 'binary' }],
    values: [
      { value: 'open', label: 'Open' },
      { value: 'closed', label: 'Closed' },
    ],
  },
];

export function HeadlessFilter() {
  const builder = useFilterBuilder({ schema });
  const viewModel = useFilterViewModel({
    filter: builder.filter,
    schema: builder.schema,
  });

  return (
    <section aria-label={viewModel.root.aria.label}>
      <button
        type="button"
        onClick={() =>
          builder.addRule(builder.filter.id, {
            field: 'status',
            operator: 'equals',
            value: 'open',
          })
        }
      >
        Add status rule
      </button>
      <pre>{formatDSL(builder.filter)}</pre>
      <pre>{JSON.stringify(viewModel.root, null, 2)}</pre>
    </section>
  );
}

DSL Editor

import type { FieldSchema, Filter } from '@x-filter/core';
import { useDslEditor } from '@x-filter/react';
import { useState } from 'react';

export function DslTextarea({
  filter,
  schema,
  onCommit,
}: {
  filter: Filter;
  schema: FieldSchema[];
  onCommit: (filter: Filter) => void;
}) {
  const [cursor, setCursor] = useState<number | undefined>();
  const editor = useDslEditor({ filter, schema, onCommit, cursor });

  return (
    <div>
      <textarea
        aria-label="Filter DSL"
        value={editor.draftDSL}
        onChange={(event) => {
          editor.setDraftDSL(event.target.value);
          setCursor(event.target.selectionStart ?? event.target.value.length);
        }}
        onSelect={(event) =>
          setCursor((event.target as HTMLTextAreaElement).selectionStart ?? editor.draftDSL.length)
        }
      />
      <button type="button" onClick={editor.commit}>
        Apply DSL
      </button>
      {editor.parseError ? <p role="alert">{editor.parseError}</p> : null}
      <ul>
        {editor.completions.map((item) => (
          <li key={`${item.kind}-${item.value}`}>{item.label}</li>
        ))}
      </ul>
    </div>
  );
}

Adapter Consumption

UI adapters such as @x-filter/antd and @x-filter/shadcn consume this layer by calling:

  1. useFilterBuilder({ schema, value, defaultValue, onChange }) for state and core mutation handlers.
  2. useFilterViewModel({ filter, schema, errors }) for renderable groups/rules.
  3. useDslEditor when a dsl editor is enabled.
  4. useReorderContract when a dnd experience is enabled.

Adapters should pass the same schema, value, and onChange contract through to consumers, expose slots for replacing atomic pieces, and preserve the ARIA metadata from the view model.