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

@kurtbruns/vector

v0.9.2

Published

A library for creating vector graphics for the browser.

Readme

Vector

Vector is a library for creating interactive math graphics on the web.

Getting Started

See the sandbox for an environment that uses the library.

Development Workflow

  1. Create a Feature Branch:

    Start development on a new feature or bug fix in a separate branch.

    git checkout -b feature/your-feature
  2. Commit Changes in the Feature Branch:

    Commit your changes regularly.

    git add . and git commit -m "Your commit message"
  3. Open a Pull Request (PR):

    Once your changes are ready, open a PR to merge your feature branch into the main branch.

    Ensure the PR undergoes code review and passes all tests.

  4. Merge the PR:

    Once approved, merge the PR into the main branch and follow the steps for publishing a new version.

    git checkout main
    git merge feature/your-feature

Publishing a New Version

  1. Commit changes in GIT: Committing changes to your codebase in Git should always come first. It provides a reference point for the changes you made.

  2. Update the version number of the library: You should update the version number of your library after committing changes to your codebase. This will ensure the new version number corresponds to the committed changes. This command also creates a new Git tag for the new version.

    • npm version patch - This will increment the PATCH version (e.g., from 1.0.0 to 1.0.1). Use this when you make backward-compatible bug fixes.
    • npm version minor - This will increment the MINOR version (e.g., from 1.0.0 to 1.1.0). Use this when you add functionality in a backward-compatible manner.
    • npm version major - This will increment the MAJOR version (e.g., from 1.0.0 to 2.0.0). Use this when you make incompatible API changes.
  3. Publish the changes to the repo.

git push origin main --follow-tags
  1. Publish the library to the npm registry: This should be the last step. After committing your changes and updating your version number, you're now ready to publish those changes to the npm registry.
npm publish