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

proder

v1.0.1

Published

A tiny lightweigh devOps tool for building production version of development directory smartly

Downloads

4

Readme

Proder

Proder is a tiny DevOps tool to build a production version of development directory smartly. (less than 3 kb !)

Proder simply separates your production version of working directory without garbadge files, source files, modules and confidential files. Rename, move and exclude files using custom configuration file. You can compress your production into zip / tar too.

All everything is in a single command!

Installation

Use the package manager npm to install Proder from your terminal

npm i -g proder

Install Proder globally to use CLI functionalities from your terminal

Commands

Show help
proder --help
# or
proder -h
Show version
proder --version
# or
proder -v

Build directory

proder --build
# or
proder -b
Compress
proder -b --compress
# or
proder -b -c       #will compress into zip
Compress custom format
proder -b --compress=tar       # zip|tar|false

Configuration

Initialize configuration
proder --init
# or
proder -i

Initilizing proder will create the default configuration file in root directory

If your configuration file is proder.config.js, then you don't need to mention file path to CLI

Configuration explaination
module.exports = {
    "src": "",                  // path to root working directory, "" means current directory; default is ""
    "build": "build",           // path to build directory or compressed file name; default is current directory name
    "compress": {               // set false to disable compressing; default is true
        "extension": "zip",     // zip | tar ; default is zip
        "level" : "high"        // high | low | medium; default is high
     },
    "exclude": [                // exclude files and directory from build; default is []
        "node_modules",
        ".git",
        "src/scss/*"            // supports regular expression
    ],          
    "move": [                   // move or rename directories or files; default is []
        [
            "from/path/block.js", "to/path/index.js"
        ] 
    ]              
}

Custom Configuration

Supports custom configuration, just mention new configuration file to cli

proder -b --config=path/to/config

You can use common_excludes list from Proder

const { common_excludes } = require("proder) 

module.exports = { 
    "build": "build",
    "exclude": [...common_excludes]
}

You can try console.log(common_excludes) to show that exactly inside the list

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change. Make a request at Proder GIT on github public repository

Please make sure to update tests as appropriate.

Published by Jafran Hasan

License

MIT Public