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/effect

v0.16.0

Published

Effect-first adapter over the proseQL WASM engine binding

Readme

@proseql/effect

Effect-first ProseQL APIs over the Rust/WebAssembly engine.

This package keeps the public TypeScript contract from @proseql/core, executes queries and mutations through @proseql/engine, wraps Promise operations as Effect and reactive results as Stream, and reconstructs public tagged errors so Effect.catchTag works. Unexpected WASM failures remain defects rather than being disguised as expected database errors.

Install

npm install @proseql/effect [email protected]

Effect is pinned exactly because this release is tested against [email protected].

Use

import { Effect, Schema, Stream } from "effect"
import { createEffectDatabase } from "@proseql/effect"

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

const program = Effect.gen(function* () {
  const db = yield* createEffectDatabase(config, { books: [] })
  yield* db.books.create({ id: "1", title: "Dune" })
  const books = yield* Stream.runCollect(db.books.query())
  yield* db.close()
  return Array.from(books)
})

const books = await Effect.runPromise(program)

Validation, not-found, storage, and other expected failures retain their ProseQL _tag and fields across the WASM boundary. Use normal Effect error operators such as Effect.catchTag.

Browser loading

Browser applications may import @proseql/effect/browser, or install @proseql/browser for that browser-safe Effect entry point plus storage hosts. The browser entry loads the packaged browser WASM; the root entry loads the Node WASM. Neither path builds Rust at runtime.

License

MIT