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

vispark-code

v1.10.1

Published

A local-first coding assistant powered by Vispark Vision

Downloads

2,331

Readme

Quickstart

bun install
bun run build
bun run start

Or install the CLI globally:

bun install -g vispark-code
vispark-code                # start with defaults (localhost only)
vispark-code --port 4000    # custom port
vispark-code --no-open      # don't open browser
vispark-code --share        # create a public share URL + terminal QR

Vispark Code opens at http://localhost:3210.

What It Is

  • A polished local coding assistant
  • Vision AI as the model backend
  • Continual Learning Available
  • An optamised harness
  • Built-in Vispark Lab API key settings
  • Project-first chats, tool flows, plan mode, and embedded terminal support

Local Data

Vispark Code stores state in ~/.vispark-code/data/.

Public share link

Use --share to create a temporary public trycloudflare.com URL and print a terminal QR code:

vispark-code --share
vispark-code --share --port 4000

--share is incompatible with --host and --remote. It does not open a browser automatically; instead it prints:

QR Code:
...

Public URL:
https://<random>.trycloudflare.com

Local URL:
http://localhost:3210

Development

bun run dev

Useful commands: The same --remote and --host flags can be used with bun run dev for remote development. --share is also supported in dev mode and exposes the Vite client URL publicly:

bun run dev --share
bun run dev --port 3333 --share

In dev, --port sets the Vite client port and the backend runs on port + 1, so bun run dev --port 3333 --share publishes http://localhost:3333. --share remains incompatible with --host and --remote. Use bun run dev --port 4000 to run the Vite client on 4000 and the backend on 4001.

bun run check
bun test
bun run dev:client
bun run dev:server
bun run sync:sources

For network access, Vispark Code binds to 127.0.0.1 by default. Use --host <hostname-or-ip> to bind a specific interface, or --remote to bind 0.0.0.0.

vispark-code --remote
vispark-code --host dev-box
vispark-code --host 192.168.1.x

The same host flags work in development, and bun run dev --port 4000 runs the Vite client on 4000 and the backend on 4001.

Project Structure

src/
  client/   React UI
  server/   Bun server, runtime bridge, Vision proxy
  shared/   Shared types and branding

Safe Source Sync

Vispark Code keeps package self-updates for installed users.

  • Your custom project files are not auto-overwritten.
  • Sync state is stored in ~/.vispark-code/data/source-sync.json.
  • Set VISPARK_CODE_DISABLE_SOURCE_SYNC=1 if you want to turn that off.