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

better-cdn-webpack-plugin

v1.1.0

Published

A webpack plugin to put bundles in a CDN

Downloads

8

Readme

better-cdn-webpack-plugin

A webpack plugin to upload assets for CDN automatically when building your app.

Install

npm install -D better-cdn-webpack-plugin
# or
yarn add -D better-cdn-webpack-plugin

Usage

const CDNWebpackPlugin = require('better-cdn-webpack-plugin');

module.exports = {
  output: {
    // ...
    publicPath: 'https://cdn.example.com/your/path',
  },
  plugins: [
    new CDNWebpackPlugin({
      getPath: () => 'your/path',
      uploadToCOS: 'tencentcloud',
    }),
  ],
};

We need to add some options in your webpack.config.js or other config files ( such as vue.config.js ).

output.publicPath

This option is important. It'll affect all your static assets' references. After the build, the asset's URL in your HTML will be something like this:

<script type="text/javascript" src="https://cdn.example.com/test/8565fe7e1364113022be/filename.js"></script>

plugin

Like other plugins, you just need to pass some options to CDNWebpackPlugin.

Options

getPath

It's a function, and it must match your output.publicPath. That means you should put things in the right place, then you can access them correctly.

When I set output.publicPath to https://cdn.example.com/some/path. My plugin's option getPath should be like () => "some/path".

uploadToCOS

uploadToCOS: (fileKey, file) => Promise

This can be an upload function or a build-in upload method name. When the plugin collects all the assets, we need to upload them to COS one by one. This option offers a way to upload your assets regardless of which COS you are using.

We have only one build-in upload method now. It's tencentcloud.

If you want to use this build-in method, you should set some env variables.

TencentCOSSecret, TencentCOSKey, TencentCOSRegion, TencentCOSBucket

Tested version

The below versions of webpack are working fine with this plugin (at least in my case).

  • v3.6.0
  • v3.11.0
  • v4.44.0, v4.44.2, v4.10.0
  • v5.10.0

Contribute

If you find out some problems with your project, please let me know! Any issues and PRs are welcome!

License

MIT