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

chmod-webpack-plugin

v0.1.3

Published

<h1 align="center">chmod-webpack-plugin</h1> <p align="center"> <a href="https://www.npmjs.com/package/chmod-webpack-plugin"><img src="https://img.shields.io/badge/npm-chmod--webpack--plugin-brightgreen.svg" /></a> <a href="https://www.npmjs.com/p

Downloads

417

Readme

This plugin allows you to set files and directories permissions after bundle compilation.

Installation

npm i --save chmod-webpack-plugin

Example

// webpack.conf.js
const ChmodWebpackPlugin = require("chmod-webpack-plugin");

module.exports = {
    plugins: [
        new ChmodWebpackPlugin([
                                   {path: "dist/dist/", mode: 660},
                                   {path: "dist/bin/**"},
                                   {path: "dist/public/", mode: 640},
                               ],
                               {
                                   verbose: true,
                                   mode:    770,
                               }),
    ],
};

Usage

// webpack.conf.js
const ChmodWebpackPlugin = require("chmod-webpack-plugin");

module.exports = {
    plugins:[
            new ChmodWebpackPlugin(config [, commonOptions])
    ]
}

config (required)

Object or array of objects

const config = {
    // Required, string or array of strings
    // Globs that match files/paths to set permissions
    path,
    
    // Same as path parameter, but ,atched paths will will be ignored
    exclude:         [],
    
    // Path that will be treated as relative root for globs
    // By default it is a webpack's directory
    root:            path.dirname(module.parent.filename),
    
    // Permissions to set
    mode:            644,
    
    // If true will output the result of each matched path processing
    verbose:         false,
    
    // If true will not generate any console output (excepting errros)
    silent:          false,
    
    // If true will only emulate permissions change
    dryDun:          false,
    
    // If true only files will be processed
    filesOnly:       false,
    
    // If true only directories will be processed
    directoriesOnly: false, 
};

common options (optional)

Object of parameters tat will be used as default for all configs.
Has the same structure with config entity, instead of .path parameter, which is ignored here.

Tests

npm i
npm run test

Coverage

npm i
npm run test:coverage