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

pre-action

v1.0.0

Published

Make a validation before any future actions

Downloads

3

Readme

Pre Action

The motivation for creating this module is to prevent any publication or any action that could harm a specific task, for example: the publication of a package to the npm registers with missing data, etc.

Installation

Local

npm install --save-dev pre-action

Global

npm install -g pre-action

Usage

pre-action [event]

Options

| Option | Type | Description | | ----------- | ----------- | ----------- | | -f | string | Format of the file (json, json5, yaml, toml, ecld) | | -c | string | Path of the file | | -n | string | Name of the file | | -s | boolean | Stop process if a required didn't found |

Example
One Level

.preactionrc

{
    "publish": {
        "file": "./package.json",
        "format": "json",
        "content": {
            "repository": {
                "required": true
            }
        }
    }
}
Nested Validation

.preactionrc

{
    "publish": {
        "file": "./package.json",
        "format": "json",
        "content": {
            "repository": {
                "required": true,
                "content": {
                    "required": true
                }
            }
        }
    }
}
Warning interface

.preactionrc

{
    "publish": {
        "file": "./package.json",
        "format": "json",
        "content": {
            "repository": {
                "warning": true
            }
        }
    }
}

If you use the 'warning' option, the dynamic interface will be activated.

Extends

We can also inherit an already established structure

.preactionrc

{
    "publish": {
        "file": "./package.json",
        "format": "json",
        "extends": "pre-action/template/npm-publish"
    }
}

List of available structures:

| name | Description | | ----------- | ---------- | | pre-action/template/npm-publish | Structure for publish packages |

Only check file

You have the option of validating only that a file exists

.preactionrc

{
    "publish": {
        "file": "./package.json",
        "format": "json",
        "exists": true
    }
}
Only check directory

You have the option to validate if a directory is empty

.preactionrc

{
    "publish": {
        "file": "./mydir",
        "isNotEmpty": true
    }
}

Call

we can call with this command

pre-action publish

and also we can combine this command with a flow

pre-action publish && npm publish

Create custom extends

Create a directory that has a file 'index.json' in the main root and establish the path of that folder or if it were the case the name of the module.

If you want to help this project, go to the github repository of this project