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

is-exact-version

v2.0.0-beta.1

Published

Simple, modern module for identifying whether a package.json "version range" string refers to an exact version

Downloads

2,595

Readme

is-exact-version

npm version build status CodeClimate maintainability rating (percent) test coverage This project uses conventional commits

This module is a complete re-write of bendrucker/exact-version. It drops support for end-of-life versions of node, is written in TypeScript, and uses Jest for testing.

Why another library?

I needed something more consistent and complete (e.g. behavior matching package.json version range string spec, including support for "commitish" values), and I first attempted to make a PR but then was met with belligerence. Making my own implementation seemed the more civil course of action than engaging in an argument.

Why should I use this library?

  • Uses node's own semver module as much as possible, and consequently uses no RegExp of its own.
  • strictNullChecks & noImplicitAny are both enabled in tsconfig.json.
  • Thorough test suite clearly indicates behavior.

Usage

Example: (try it on RunKit)

import { isExactVersion } from "is-exact-version";

const examples = [
  '^1.0.0',
  '~1.1.0',
  '1.1.1',
  '1.0.0-beta.1',
  'user/is-exact-version#commit'
];
for (const s of examples) {
  console.log(`${s} -> ${isExactVersion(s)}`);
}

// Log:
// "^1.0.0 -> false"
// "~1.1.0 -> false"
// "1.1.1 -> true"
// "1.0.0-beta.1 -> true"

Requirements

  • Node >= 16.* (>= 12.* should work, but is not tested) For older versions use the 1.x version of this package.

Support / questions

If you have any questions or suggestions related to this package feel free to create a new issue. However, it should be noted that I have not actually needed to use this for a long time, and the main reason I keep it around is for practice ("kata" if you will), e.g. learning to use GitHub Actions as well as ESM in TypeScript.

Development

This package (optionally) uses debug-js/debug and will output debugging information if the DEBUG environment variable enables is-exact-version. e.g.

$ DEBUG=is-exact-version node some-app.js

Not that that's particularly useful for most people...

This project also strives to adhere to the conventional commits standard.

License

This project is licensed under the terms of the open source MIT License. See LICENSE for the complete text.