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

app-versioner

v1.0.6

Published

Helper for adding versioning to you app

Downloads

9

Readme

app-versioner

Versioning helper for static assets. Useful for adding versioning (eg dist/1-0-4/css/main.css) to your output to make browser cache busting and version tracking easier.

Example usage

Configure SCSS variables for build path and environment in _vars.scss before you do a Sass build.

const AppVersioner = require('app-versioner').AppVersioner;

const IS_PROD = process.env.NODE_ENV === "production";
var appVersioner = new AppVersioner("/dev-environment/", "/prod-environment/", IS_PROD);

appVersioner.setScssBuildPath("app/scss/_vars.scss"); // $build-path: "/dev-environment/1-0-1/";
appVersioner.setScssEnv("app/scss/_vars.scss"); // $environment: "dev";

If you don't wish to include the versioning in the scss variable (maybe your dev environment doesn't really need it), you can pass false in 2nd parameter

appVersioner.setScssBuildPath("app/scss/_vars.scss", false); // $build-path: "/dev-environment/";

You can get the versioned path for your sass build like this ("bld" is short for "build directory" and accepts an string parameter)

var cssDir = appVersioner.bld("css");

If you need more control, you can choose to include the versioned folder or not like this

var includeVersioning = process.env.NODE_ENV === "production";
var cssDir = appVersioner.getBuildPath(includeVersioning) + "css"; // "/dev-environment/1-0-1/css/"

Or copy files after your production or development versioned folder like this

appVersioner.copyToBuildPath("app.css");

Or copy entire folders (pass true to 2nd parameter if you want to include the last folder - in this example "/js/" would be included in the output)

appVersioner.copyToBuildPath("dist/js/", true);