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

webpack-post-compile-plugin

v1.2.3

Published

A webpack post compile plugin

Downloads

398

Readme

webpack-post-compile-plugin Build Status codecov.io

A webpack post compile plugin. It is used to include post compile modules in node_modules.

Install

npm i webpack-post-compile-plugin --save-dev

Usage

const PostCompilePlugin = require('webpack-post-compile-plugin')
const path = require('path')

module.exports = {
  // ...
  module: {
    rules: [
      // ...
      {
        test: /\.js$/,
        loader: 'babel-loader',
        include: [path.resolve(__dirname, './')]
        // eg: {"compileDependencies": ["cube-ui"]} // package.json
        // the current rule's loader will process node_modules/cube-ui/**/*.js too
      }
      // ...
    ]
  },
  plugins: [
    new PostCompilePlugin()
  ]
}

Config

And if you can control all the packages which you want to post compile, you can just add postCompile: true to the packages package.json:

{
  "name": "your-one-pkg",
  // ...
  "postCompile": true
  // ...
}

Or you can add compileDependencies to your application package.json:

{
  "name": "your-application",
  // ...
  "compileDependencies": ["xx-pkg"]
}

After 1.0.0+, you can alse use postCompile like this:

{
  "name": "your-one-pkg",
  // ...
  "postCompile": "src/*.js"
  // ...
}
{
  "name": "your-one-pkg",
  // ...
  "postCompile": [
    "*.js"
  ]
  // ...
}

1.0.0+ postCompile uses micromatch to match the post compile files.

Options

new PostCompilePlugin({
  dependenciesKey: 'myCompileDependencies',
  compileDependencies: ['a', 'b'],
  compilePaths: ['node_module/@test']
})
  • dependenciesKey {String} default 'compileDependencies', dependencies key in package.json, it is used to find and include post compile node modules.

  • compileDependencies {Array} default undefined, application init post compile node modules, if it is undefined then the plugin will get dependenciesKey value or dependencies keys value in package.json as the init application's post complie node modules.

  • sourceDir {String} 0.5.1+ default src, application source directory, if your application's source directory is lib you should set this config to lib.

  • compilePaths {Array} 1.1.0+ default undefined, a dependencies matching any of these conditions will be treated as post compile modules.