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

npm-version-nonroot

v1.0.0

Published

npm-version for packages in subdirectories of git repositories

Downloads

6

Readme

npm-version-nonroot

npm version for packages in subdirectories of git repositories

Use case

I've started building projects that utilize Docker and organizing the repositor ies based on the Docker containers. A simple project might have the following structure:

project
├── db
|   ├── Dockerfile
|   └── schema.sql
├── web
|   ├── Dockerfile
|   ├── package.json
|   └── server.js
├── docker-compose.yml
└── README.md

Because package.json is not in the root of the git repository, npm vesion will not perform any of the git-related commands, such as committing and tagging. This module makes npm version work as expected.

Usage

Add nvn-preversion and nvn-version as part of npm's preversion and version scripts, respectively.

"scripts": {
  "pre-version": "nvn-preversion",
  "version": "nvn-version"
}

Implementation details

nvn-preversion runs the following steps. All differences from standard npm preversion behavior are noted.

  1. Check if the git working directory is clean.
  • npm version would normally do this before running the preversion script.
  • nvn-version does not yet support the --force flag to prevent this check.

nvn-version runs the following steps. All differences from standard npm version behavior are noted:

  1. Update npm-shrinkwrap.json if it exists.
  • npm version would normally run this, and all following steps after the version script and before the postversion script.
  1. Commit the changes to git.
  2. Create the tag in git.
  • nvn-version does not yet check for an existing tag of the same name.

License

Copyright Scott González. Released under the terms of the MIT license.