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

@spinodev/copy-webpack-plugin-cached

v6.1.0

Published

Copy files && directories with webpack

Downloads

45

Readme

copy-webpack-plugin-cached

This is a personal use fix for the original https://www.npmjs.com/package/copy-webpack-plugin which does not work properly for me.

Changes

I found that the copy plugin just always overwrites the files in my dist directory, so from logging i figured that "compilation.getAsset" and "compilation.updateAsset" weren't recognizing any existing files in the dist folder before the compilation (meaning they only recognized the files after they were copied again during the current compilation).

My fix:

Added a cache file that saves mappings of (filePath, size) using fs. By default the path to this cache file is in node_modules folder, so you should overwrite that location.

Added a new var to the plugin constructor - "cacheLocation" - the path to where you want the cache file to be(including the cache file name).

example:

new CopyPlugin({
    patterns:
        [
            {
                from: path.resolve(__dirname, './assets'),
                to: path.resolve(__dirname, './dist/assets'),
                force: false,
            },
        ]
        , options: {
            cacheLocation: path.resolve(__dirname, "./asset_cache/copy_cache"),
        }
}),

License

All credits and license to the creators of the original plugin: MIT