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

semantic-release-verify-deps

v1.0.2

Published

verify dependencies plugin for semantic-release

Downloads

30

Readme

Semantic-release-verify-deps

semantic-release plugin to validate the format of dependencies before releasing.

Why create this plugin

In the typical gitflow process, we release tags on master branch and we implement on develop branch.

When doing implementation we sometimes need to change deps to 'floating' deps like :

Even if this is useful on dev branch, it is a bad idea to release on master branch a version with floating dependencies.

Current plugin lets you define a validation/regular expression pattern to avoid this kind of mistake.

Installation

npm install --save-dev semantic-release-verify-deps 

Usage

Plugin must be set within the plugin definition in the Semantic-release configuration file on Verify Conditions step in the project's package.json file.

For example, you can force each dependency to finish with a digit in package.json by doing :

"release": {
    "verifyConditions": [
      {
        "path": "semantic-release-verify-deps",
        "dependencies": true,
        "devDependencies": false,
        "regExps": [
          "\\D$"
        ]
      }
    ]

Configuration

Parameters:

|Parameter|Description|Type|Default| |---------|-----------|----|---| |dependencies|dependencies that are specified in package.json file| boolean| true| |devDependencies|dependencies that are specified in package.json file| boolean| false| |regExps|regular expresions that will be used as pattern in RegExp Constructor to match invalid dependencies in package.json file | array of patterns| [] |

Regexps examples

"\\D$" : Each dependency ending without a digit is invalid for release

"\\d$" : Each dependency ending with a digit is invalid for release

".*github.*" : Each github dependency is invalid for release