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

@gleanql/vite

v0.1.7

Published

Glean's Vite plugin: provisions the runtime, runs codegen and compiles route reads to GraphQL operations

Readme

@gleanql/vite

The build plugin for GleanQL — GraphQL without writing GraphQL. This is the only build wiring an app needs:

// vite.config.ts
import { glean } from "@gleanql/vite";

export default defineConfig({
  plugins: [glean({ schema: "./schema.graphql" }), redwood()],
});

On every build and dev start it generates the schema-specific runtime into @gleanql/client: the typed glean accessor, branded schema types, the compiled operations (one per route, extracted from your components' field reads), and the persisted-operation manifest. In dev it also serves the /__glean devtools page and recompiles operations live as you edit.

Options

| Option | Default | What it does | |---|---|---| | schema | — | path to your .graphql SDL (required) | | framework | "rwsdk" | "rwsdk", "react-router", or a custom preset | | endpoint | "/graphql" | URL the client POSTs to | | persisted | false | send operations by sha-256 hash; pair with createPersistedResolver | | operations | — | a module of hand-built buildQuery operations to register | | gcKeepPages | off | staleness-aware cache GC on navigation | | masking | false | dev warning when a component reads outside its compiled read-map | | maxCacheRecords | unbounded | LRU cap on the client cache | | strict | false | fail the build on any compiler diagnostic | | backend | "typescript" | type engine ("tsgo" = experimental Go-native) |

Docs

Full documentation lives in the GleanQL repo — run pnpm docs there, or start with the Get Started guide.

MIT