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

@vishot/core

v0.2.0

Published

Shared Vishot capture contracts and artifact helpers.

Readme

@vishot/core

Shared capture contracts and artifact helpers for Vishot.

What it does

This package owns the reusable protocol shared by source adapters, renderers, and mockup packages:

  • artifact types and image artifact creation
  • artifact file path normalization and uniqueness checks
  • capture-root selector generation
  • browser ready signals
  • capture-name derivation from browser URLs
  • artifact transformer sequencing

How to use

import { captureNameFromUrl, captureRootSelector, markScenarioReady } from '@vishot/core'
import { createImageArtifact } from '@vishot/core/artifacts'

Use captureRootSelector(name) to mark DOM regions for browser export, and markScenarioReady() when a scene has finished layout, navigation, and data loading.

Use captureNameFromUrl(url) when direct page capture should derive a stable artifact name from a pathname or hash route.

When to use

  • You are writing a Vishot source adapter or renderer.
  • You need stable artifact metadata or filename behavior.
  • You need shared capture-root or ready-signal helpers.

When not to use

  • Use @vishot/cli for command-line capture workflows.
  • Use a source or renderer package when you need runtime-specific Playwright behavior.