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 🙏

© 2024 – Pkg Stats / Ryan Hefner

visably-search-lib

v1.0.11

Published

provides access to common tooling needed across repositories supporting search

Downloads

4

Readme

visably-search-lib

provides access to common tooling needed across repositories supporting search

Development

run npx tslint --project . && npx prettier "src/**/*.ts" --list-different before pushing your changes to make sure you've not introduced any issues.

Releasing (merging to master)

all use of this npm library has pinned the branch master and, as such, before pushing/merging to master the package must be prepared accordingly before going out.

usually this just requires running:
(note: make sure you commit your changes before running this)

npm run prepare-release (this will open a rebase editor prompt; you can simply write+quit from the editor)

followed by:

git push --follow-tags origin master

TODO:

  • need add unit tests (update prepare-release script once done to also run test:unit)