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

bumpver-webpack-plugin

v1.0.5

Published

A webpack plugin to bump the major, minor, or patch number for a build

Downloads

2

Readme

bumpver-webpack-plugin

A webpack plugin to bump the major, minor, or patch number for a build.

Install

npm install bumpver-webpack-plugin --save-dev

or

yarn add bumpver-webpack-plugin --dev

Usage

Increments patch number by default, but you can specify either major, minor, or patch.

Arguments:

  • files (required): one or more file names containing "version" to increment
  • level (optional): semver level - 'major', 'minor', or 'patch'

To use default settings and increment patch for every build...

const BumpVerPlugin = require('bumpver-webpack-plugin');

module.exports = {
    plugins: [
        new BumpVerPlugin({
            files: ['package.json']
        })
    ]
}

To specify semver level ("major", "minor", or "patch") for every build...

const BumpVerPlugin = require('bumpver-webpack-plugin');

module.exports = {
    plugins: [
        new BumpVerPlugin({
            files: ['package.json'],
            level: 'patch'
        })
    ]
}

To pass a semver level to your webpack config, set variable via env parameter like this...

const BumpVerPlugin = require('bumpver-webpack-plugin');

module.exports = (env) => {
    return {
        plugins: [
            new BumpVerPlugin({
                files: ['package.json', 'manifest.json'],
                level: env.VERSION_LEVEL
            })
        ]
    }
}

Then, in your call to webpack add a variable to env containing the semver level to increment...

"scripts": {
    "build-major": "webpack --env.VERSION_LEVEL=major",
    "build-minor": "webpack --env.VERSION_LEVEL=minor",
    "build": "webpack"
}

As per the semver spec, when you increment minor the patch value will be reset to 0. When you increment major both the minor and patch will be reset to 0.

Plugin based on original bump-webpack-plugin by johnagan. Expanded functionality to include semver level.