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

lit-query-core

v0.0.1-alpha

Published

LitElement bindings for [@tanstack/query-core](https://www.npmjs.com/package/@tanstack/query-core).

Readme

lit-query

LitElement bindings for @tanstack/query-core.

A tiny library which exposes the intuitive API of @tanstack/query, similarly to react-query et al.

Features

Only the essentials are implemented for now.

Equivalents are exposed for

  • QueryClientProvider
  • useQueryClient
  • useQuery
  • useMutation

Usage

If you've ever used react-query the interface is familiar. lit-query exposes a few decorators to provide the query client to a component tree and to consume queries and mutations.

Setup the query client

Create a query client and provide it to your component tree like so:

import { QueryClient } from "@tanstack/query-core";
import { provideQueryClient } from "lit-query";

@customElement("my-app")
export class MyApp extends LitElement {
  @provideQueryClient
  client = new QueryClient();

  render() {
    return html`...`;
  }
}

The QueryClient comes from the core library and manages its own query cache. Any component which wants to use queries/mutations needs to have access to it. This decorator uses context (similarly to React's context) to make the client available.

Consume queries and mutations

You use queries and mutations with the consumeQuery and consumeMutation property decorators. You use them on a property which will represent the state of the query. Like so:

@customElement("todos-list")
export class TodosApp extends LitElement {
  @consumeQuery(["todos"], () => fetch(`/api/todos`).then((res) => res.json()))
  query?: QueryObserverResult<{ todos: Todo[] }>;
  
  @consumeMutation({ mutationFn: (todo: Minimal<Todo>) => toggleTodo(todo) })
  toggleMutation?: Mutation<Todo, unknown, Partial<Todo> & { id: string }>;

  render() {
    return html`...`;
  }
}

Accessing the QueryClient in mutation callbacks

In React, hooks are used in a shared scope where it is easy to call useQueryClient and access the client in a subsequent useMutation. A common use-case for this is setting query data with the result of a mutation.

In Lit things work differently, so instead, the QueryClient is always provided by lit-query as part of the mutation context.

Here's an example:

@consumeMutation({
  mutationFn: (todo: Minimal<Todo>) => toggleTodo(todo),
  onSuccess: (result, _vars, context) => {
    context?.client.setQueryData(
      ["todos"],
      produce<{ todos: Todo[] }>(({ todos }) => {
        const item = todos.find((item) => item.id === result.id);
        if (item) Object.assign(item, result);
      })
    );
  },
})
toggleMutation?: Mutation<Todo, unknown, Partial<Todo> & { id: string }>;

Under the hood

The decorators exposed by this library work by attaching Reactive Controllers to components.