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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@automerge/automerge-repo-solid-primitives

v2.5.1

Published

Access Automerge Repo in your SolidJS application

Downloads

292

Readme

Solid Automerge

Solid primitives for Automerge.

pnpm add solid-js @automerge/automerge-repo @automerge/automerge-repo-solid-primitives

useDocument ✨

Get a fine-grained live view of an automerge document from its URL.

When the handle receives changes, it converts the incoming automerge patch ops to precise solid store updates, giving you fine-grained reactivity that's consistent across space and time.

Returns [doc, handle].

useDocument<T>(
    () => AutomergeURL,
    options?: {repo: Repo}
): [Doc<T>, DocHandle<T>]
// example
const [url, setURL] = createSignal<AutomergeUrl>(props.url)
const [doc, handle] = useDocument(url, { repo })

const inc = () => handle()?.change(d => d.count++)
return <button onclick={inc}>{doc()?.count}</button>

The {repo} option can be left out if you are using RepoContext.

createDocumentProjection

Get a fine-grained live view from a signal automerge DocHandle.

Underlying primitive for useDocument.

Works with useHandle.

createDocumentProjection<T>(() => AutomergeUrl): Doc<T>
// example
const handle = repo.find(url)
const doc = makeDocumentProjection<{ items: { title: string }[] }>(handle)

// subscribes fine-grained to doc.items[1].title
return <h1>{doc.items[1].title}</h1>

makeDocumentProjection

Just like createDocumentProjection, but without a reactive input.

Underlying primitive for createDocumentProjection.

makeDocumentProjection<T>(handle: Handle<T>): Doc<T>
// example
const handle = repo.find(url)
const doc = makeDocumentProjection<{ items: { title: string }[] }>(handle)

// subscribes fine-grained to doc.items[1].title
return <h1>{doc.items[1].title}</h1>

useDocHandle

Get a DocHandle from the repo as a resource.

Perfect for handing to createDocumentProjection.

useDocHandle<T>(
    () => AnyDocumentId,
    options?: {repo: Repo}
): Resource<Handle<T>>
const handle = useDocHandle(id, { repo })
// or
const handle = useDocHandle(id)

The repo option can be left out if you are using RepoContext.

context

If you prefer the context pattern for some reason, you can pass the repo higher up in your app with RepoContext

RepoContext

A convenience context for Automerge-Repo Solid apps. Optional: if you prefer you can pass a repo as an option to useDocHandle and useDocument.

<RepoContext.Provider repo={Repo}>
  <App />
</RepoContext.Provider>

useRepo

Get the repo from the context.

useRepo(): Repo

e.g.

const repo = useRepo()