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

allow-publish-version

v1.0.0-rc.1

Published

Publish package with allowed versions only

Downloads

5

Readme

Allow Publish Version

Allow Publish Version util protects your NPM package from being accidentally published with invalid version. Use it with prepublishOnly script of package.json.

It will check your package version to be valid NPM subset of semver with exact prerelease record. Valid versions might look like 1.0.0 or 1.0.0-beta.1.

Installation

npm i allow-publish-version

Usage

  1. Add prepublishOnly script in package.json.
  2. Run npm publish when you're ready to publish your package, or npm publish --dry-run to test.

Example package.json:

{
  "version" : "1.0.0-alpha.1",
  "scripts": {
    "prepublishOnly": "allow-publish-version"
  },
}

By default there will be alpha, beta and rc prereleases allowed.

Examples

Valid versions:

1.0.0
1.0.0-pre.1
1.0.0-pre.beta.1

Invalid versions:

1.0 # Not a valid semver.
1.0.0-beta # No prerelease version.
1.0.0-pre.0 # Prerelease index should start from 1.
1.0.0-pre.1.0 # Prerelease name couldn't contain numbers.
1.0.0-beta.0+x64 # Builds are not supported by NPM.

Configuration

APV could be configured to use another prerelease scheme with package.json.

{
  "version" : "1.0.0-nightly.1",
  "scripts": {
    "prepublishOnly": "allow-publish-version"
  },
  "allowPublishVersion": {
    "prereleases": ["nightly", "beta"]
  }
}

API

AllowPublishVersionRecord

AllowPublishVersionFlag | AllowPublishVersionList | AllowPublishVersionDict

Configuration value AllowPublishVersionRecord describes the value of allowPublishVersion field of package.json.

AllowPublishVersionFlag

true

Boolean value true turns default APV configuration on.

Example:

{
  "allowPublishVersion": true
}

AllowPublishVersionList

Array<string>

Array should contain allowed prerelease names or picomatch-compatible glob patterns.

Example:

{
  "allowPublishVersion": ["beta", "pre.*"]
}

AllowPublishVersionDict

{
  prereleases: Array<string>
}

Dictionary holds single field prereleases. This field contains allowed prerelease names or picomatch-compatible glob patterns.

Example:

{
  "allowPublishVersion": {
    "prereleases": ["beta", "pre.*"]
  }
}

License

MIT.