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

@proseql/engine

v0.16.0

Published

Promise-first WASM engine binding for proseQL

Readme

@proseql/engine

Promise-first ProseQL database execution in Rust compiled to WebAssembly.

@proseql/core defines the shared TypeScript schema and data contract. This package compiles that supported schema subset into an engine descriptor, loads the packaged WASM, and exposes Promise-based query, mutation, persistence, and watch APIs. It does not fall back to a separate JavaScript query engine.

Install

npm install @proseql/engine [email protected]

The package is tested with exactly [email protected] because database schemas come from Effect Schema.

Node

import { Schema } from "effect"
import { createEngineDatabase } from "@proseql/engine"

const config = {
  books: {
    schema: Schema.Struct({ id: Schema.String, title: Schema.String }),
    relationships: {},
  },
} as const

const db = await createEngineDatabase(config, { books: [] })
await db.books.create({ id: "1", title: "Dune" })
const books = await db.books.query()
await db.close()

The Node entry point loads the Node-targeted JavaScript glue and .wasm file included in the npm package. Consumers do not need Rust, wasm-bindgen, or a repository checkout at runtime.

Browser

Import the browser-safe loader from @proseql/engine/browser:

import { createEngineDatabase } from "@proseql/engine/browser"

A browser or bundler loads the included browser WASM asset through import.meta.url. Do not copy a WASM file from a different package version: the loader rejects stale generated bindings. Applications that also need browser persistence normally install @proseql/browser, which re-exports this browser engine and provides localStorage, sessionStorage, and IndexedDB hosts.

Effect API

Install @proseql/effect when application code should receive Effect and Stream values instead of Promises. It uses this same Rust/WASM engine and reconstructs public tagged errors for Effect error handling.

License

MIT