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

git-sbt

v0.1.0

Published

A lightweight git subtree wrapper.

Downloads

3

Readme

Development

In order to test the package locally, run npm run build && npm link. Since this installs the current repo to the global node_modules directory, I recommend using nvm in order to keep the these testing packages separate from your normal global node_modules. If you do use nvm, run these commands after cloning the repo:

nvm install v17.1.0 # This is the node version the project uses.
nvm alias git-sbt v17.1.0

Then, while inside the root directory of this project, run nvm use to enable the node environment with the git-sbt testing packages. Run nvm link git-sbt to install a local testing git-sbt version to another project. Run npm run test:remove to remove the testing packages from the global node_modules directory.

Later we need to add npm pack support.