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

@vessel-dsp/core

v0.6.14

Published

Headless VesselDSP circuit, device, format conversion, and layout model APIs.

Readme

@vessel-dsp/core

Headless VesselDSP circuit, device, format conversion, and layout model APIs.

This package has no React, DOM rendering, AudioContext, or AudioWorklet dependency.

.vdsp is the portable CircuitDocument source for hosts that want an inspectable schematic and a simulatable circuit. Core preserves source-visible components, layout, controls, and metadata so downstream apps can show a source-like schematic view while their own runtime lowers that graph into MNA, kernel, or macro DSP execution. Source-trace ledgers, private artifact paths, and provenance-only evidence should stay in the consuming project's packet or catalog metadata instead of being embedded in the portable .vdsp.

.vdsp parsing supports current circuit-interchange/v3 documents, preserving reviewed physical build metadata such as build scope, mechanical envelopes, BOM rows, embedded part and footprint catalogs, off-board wiring, panel drill placement, and board realizations for stripboard, perfboard, breadboard-pattern protoboard, and fabricated PCB.

Conversions from v3 .vdsp to formats that cannot represent those physical fields throw by default. Use convertCircuitDocumentFileWithReport() with lossPolicy: 'drop-with-diagnostics' when intentional lossy export is needed.

Core validates semantic ControlRole values on source component properties and controlInterfaces[].controlRole. Roles are optional for source/read-only schematics; unknown roles warn by default and become errors when callers pass validateDocument(document, { playbackClaim: true }). Hosts can add lowering-specific diagnostics with validateDocument(document, { rules: [...] }) without embedding runtime policy in core.