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

@isaacadams/versioner

v0.2.4

Published

a light-weight version management system built using node.js

Downloads

4

Readme

Versioner

a light-weight version management system built using node.js

Usage Information

Usage: versioner [options] [command]Versioner, helping developers manage their versionsOptions:  -V, --version  output the version number  -h, --help  output usage informationCommands:  init   initialize versioner for your project  get [options]  Get the current version

to do

  • init requires project name and initial version
  • on init
    • master will be tagged with initial version
    • release branches will be generated
  • on release
    • master will be tagged with new version
    • versioner will always looks to master tags for the current version
  • add 'long version' or 'with suffix' options to 'get'

problems

  • none

plans

  • versioner will be a CLI
  • will be able to
    • bump local build #s
    • create release branches with latest release versions
    • when releasing, will be able to bump version number

thoughts

  • starting a new release
    • does making a new release branch drive the new release version?
    • will versioner have a command that starts a new release and creates a release branch
  • is there a way to synchronize jenkins and versioner with build #
  • will there be three release branches at at time? One for the next major, minor and patch?
    • versioner could create the three release branches and always have them exist until they release
    • each one will continually integrate into the next one up
    • how do I know that a package has been released?
    • each release branch gets created underneath release/${project-name}/* when the support for mutli project repos is needed