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

dev-build-release

v0.1.4

Published

Simple tool to append the build number to the package.json for a development release

Downloads

478

Readme

dev-build-release

Small script to append the build number to the version number

Usage

You must use dev-build-release in a folder with a package.json and a remote to push to.

dev-build-release -b BUILD_NUMBER -g BRANCH_NAME

Updates version of package.json to a "feature" branch version schema

dev-build-release -b BUILD_NUMBER

Updates version of package.json to a "development" branch version schema

dev-build-release -o 1.2.3

Updates version of package.json to a hardcoded version(1.2.3, in the above example)

determine-version

Outputs message about what repositories to update and what the version of this project should be

Usage

determine-version

Outputs dependency version range that should be used in repositories that depend on your repository

determine-version -p comma-delimited,list,of-parent-repos

Outputs message of what repositories should be updated and what version range should be used

Post Commit Git Hook

To make repository print out this message whenever a user makes a commit

  • Add dev-build-release and ghooks as dependencies to package.json
npm install ghooks dev-build-release --save-dev
  • In package.json, add the following configurations. Replace <parentRepos> with names of repositories that depend on your repository
"scripts": {
    "determineVersion": "node ./node_modules/dev-build-release/bin/determine-version -p <parentRepos>",
},
"config": {
    "ghooks": {
        "post-commit": "npm run determineVersion"
    }
}

generate-version-file

Generates a version.json file based on package.json and other build information

Usage

generate-version-file

Post Build Step

  • Add dev-build-release as a dependency to package.json
npm install dev-build-release --save-dev
  • In package.json, add the following to "scripts"
"scripts": {
    "version-file": "node ./node_modules/dev-build-release/bin/generate-version-file"
}
  • The last step is dependent on how the repository actually is built. You will need to add either a "pre" or "post" step for anything that builds the repository.

    • For example, a repository can be built via the "start" or "build" script.
    • Your repository will need to add npm run version-file to both "prestart" and "postbuild" to ensure that the version.json file is created whenever the repository is build