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

version-file

v0.1.0

Published

Generates a file with your apps name, version and build date

Downloads

5

Readme

version-file

Code Climate

Generates a file with your package name, version and build date.

Use case

The intention of this module is to provide insight into when a certain version of an app was deployed (typically web apps).

For example, lets say you are working on a team of where not everyone has access to the source code or the ability to trigger deployments (like designers, testers, marketers, project managers, etc).
At some point, one of these folks might need to know when the latest version of something was deployed (either to answer a customers question or compare environments or what have you).
By taking a glace and the version.txt file in their browser, they can quickly get that type of information with out having to disrupt the busy developers or waiting for somebody to get back to them.

Sample outfile file content

version-file v0.1.0
Build date: Fri May 02 2014 00:10:42 GMT-0400 (EDT)

Available config options:

(these are all optional)

  • pathToOutputFile: where you write the file content, includes the file name (defaults to 'version.txt' in the root directory')
  • pathToTemplate: file path to an external EJS template file
  • templateString: a raw template string to be used in the file output (available as an alternative to using an external template file)
  • extras: an object intended to hold any additional data you wish to utilize in your templating (see the template section for more details)

Templating

This modules uses EJS as its templating system. As indicated in the config options section, you can utilize your own template by either (a) passing in a path to an external file or (b) typing the template in-line.

The available options are:

  • name: the package name (based off the content of your package.json file)
  • version: the version number (also based off the content of your package.json file)
  • time: a human-readable time stamp
  • extras: an object containing any custom / additional data that is needed in the template

Sample template:

<%= name %> v<%= version %>
Build date: <%= time %>

<%= extras.teamName %>