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-flow-db

v1.6.0

Published

Storage of documents in database using git-a-like flow and versioning. Now on top of mongoDB

Downloads

6

Readme

git-flow-db

Allows to store file versions using git-a-like-flow in database. So you can combine git way of thinking and mongodb replication. I needed that for configuration in one of my projects.

Idea

  • It's file centric (doesn't have tree)
  • Git SHA1 are skipped as overkill here, MongoIDs are reliable enough
  • Repo/File information is stored in __git_flow_repos
  • Objects are stored in __git_flow_objects as raw versions
  • Index is stored in __git_flow_index
  • As in git you have one current head per repo

Install

npm install --save git-flow-db

Index

{
    "org" : "organisation",
    "doc" : "file",
    "version" : "979ffd132438c2313b1c51317d57d84c432553c8",
    "branch" : "master",
    "parent" : "517b101d97ed94afa87beb0bdeb357fb38af8ec1",
    "merge" : "fd996410cb9163cc01aee107e4d4320d189a5c7d",
    "committer" : "lukasz",
    "date" : "2012-04-23T18:25:43.511Z",
    "message" : "Merged",
    "org": 32
}

Next steps

  • Fork/Merge
  • Current head in __git_flow_index to allow search

Contribute

Fork -> Dev -> Test (CC >= 98.52%) -> Commit -> Pull Request -> Repeat

License

MIT - because it's fun to share