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

vivth

v1.4.10

Published

library primitives

Readme

HOW TO INSTALL

  • example uses npm, you can allways use your own favourite package manager;
npm i vivth

vivth

  • vivth are intended to be a collections of usefull primitives, and not to be directly used as underlying framework;
  • vivth are leaning to esm(.mjs)+jsdoc first;
    • some functionality "might need" work around if you are using other than esm+jsdoc;
    • CompileJS, ESBundler expose format option for some leeway for commonJS;
  • completely JSruntime agnostic:
    • instead of vivth trying to guess, all runtime specific API should be provided by dev;
  • contains helpers to help you write data driven javascript program, including:
    • collections of extremely ⚡ performant signal classes;
      • vivth deliberately take away auto-subscription:
        • and introducing more imperative way of subsrciption yet still simple enough, which in turn, it completely removes total code blocking on previously needed auto subsrciption process on first run;
        • and also make previously unthinkable dynamic subscription on conditionals that runs outside first run, now completely possible;
    • collections of queue-helper classes;
    • fully typed worker-threads abstraction;
    • error as value function helper;
    • opionated autoDocumentation;
    • opionated bundler:
      • abstracted via esbuild;
    • opionated compiler;
      • abstracted via pkg, deno, and bun;
  • when using runtime that doesn't provide specific common modules golbally(like Deno), dev should import it statically from node:module_name, example:
    import process from 'node:process';

versions:

  • 1.0.0+:beta:

    • beta release;
    • checking edge cases;
    • stable API, the exposed API access are highly unlikely to changes, only the underlying code might changes for improving performance;
  • 1.3.x:beta:

    • type should now fully fixed, even with strict ts check;
  • 1.3.3+:beta:

    • added class Dev for testing and Dev/preBundled only code block;