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

@powersync/diagnostics-ui

v0.0.2

Published

Host-neutral Vue UI for PowerSync live-attach diagnostics, driven by the Diagnostics Port.

Readme

PowerSync Diagnostics UI

@powersync/diagnostics-ui is the PowerSync DevTools UI: a Vue 3 panel that shows the live state of a PowerSync client.

Internal package. PowerSync SDKs and tools depend on it. Do not add it to your app. Use @powersync/diagnostics instead.

Every host shows the same build. The panel reads data only through an SdkIntegration from @powersync/diagnostics-core. It imports nothing from any PowerSync SDK and knows no host.

Tabs

  • Sync Status: connection state, sync progress, the upload queue, priority sync, and a "Sync now" checkpoint request.
  • Data Inspector: a searchable table and view tree, and a SQL console with syntax highlighting.
  • Buckets: per-bucket downloaded and total operations, size, and a drill-down into a bucket's operations.
  • Streams: sync stream subscriptions with progress, TTL, and priority, and a subscribe/unsubscribe form.
  • Config: connection details and the schema as a tree or JSON.
  • Logs: client logs with a level filter and search.

Embed the built page

dist/standalone/ is a self-contained page. It gets its SdkIntegration in one of two ways, in this order: from a devframe host that serves it (the @powersync/diagnostics definition), or from a parent page that hands it a MessagePort with attachIframe from @powersync/diagnostics-core. Only this bootstrap (standalone/) knows about devframe. The components in src/ take an SdkIntegration and nothing else.

Use the component

To render the panel inside your own Vue app, provide an integration and mount the panel:

<script setup lang="ts">
import { DiagnosticsPanel, provideDiagnostics } from '@powersync/diagnostics-ui';
import '@powersync/diagnostics-ui/style.css';
import { integration } from './integration';

provideDiagnostics(integration);
</script>

<template>
  <DiagnosticsPanel />
</template>

provideDiagnostics also accepts a Promise<SdkIntegration>, for a host that gets its integration after setup.

A host that owns the theme passes it as an option: provideDiagnostics(integration, { theme: 'dark' }). The value can be a string, a ref or a getter. The panel then follows it, hides its own toggle and stores nothing. The standalone page takes the theme in two ways: ?theme=dark|light on its URL, or a message event { type: 'powersync-diagnostics:theme', theme: 'dark' | 'light' } posted to its window. Use the message when the host learns the theme later or changes it at runtime.

Development

pnpm --filter @powersync/diagnostics-ui dev

This opens a playground at http://localhost:5199. It runs the panel over a mock integration, with no backend. Add ?noclient to see the screen shown when no client is found, or ?theme=dark to see a host-controlled theme.