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

new-version

v1.0.8

Published

A package which is frequently updated to a new version

Downloads

6

Readme

New Version

A package helps you to test if you lock version the right way.

Problem

Have you ever in a situation when one of your dependencies get updated, then it breaks your application. Then you try to lock version of that dependency. But it's hard to verify if your method of locking version is correct. new-version helps you by regularly update to a new version (currently: weekly), so you can verify if you do it the right way.

Usage

You can use node api or cli to check the current and newest version of package

Using CLI

Add this to your package.json

"scripts": {
  "new-version": "new-version"
},

then execute

npm run new-version

or simply

./node_modules/.bin/new-version

Using Node API

import NewVersion from 'new-version'

NewVersion.log();

Output:

Current version:  0.0.1
Newest version: 0.0.2

Demo

You can verify if your locking mechanism is configured correctly by including this script in index.js

// index.js
import NewVersion from 'new-version'

async function checkVersion() {
  const currentVersion = NewVersion.getCurrentVersion();
  const newestVersion = await NewVersion.getNewestVersion();
  if (currentVersion === newestVersion) {
    console.warn('You are installing newest package. Ignore if you just install this package within a week. Otherwise, you may want to check if you are locking version correctly')
  }
}

checkVersion();

API

getCurrentVersion

Return current installed version of new-version

getNewestVersion

Return newest version of new-version. This is an async function

log

Friendly log current version and newest version of new-version