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

next-plugin-cdn

v0.1.1

Published

This library is a plugin for Next.js that automatically uploads your static assets to a specified CDN during build time and configures your Next.js application to use the specified CDN prefix. This makes it easy to set up and optimize your assets for bett

Downloads

68

Readme

Next.js Plugin CDN 🌐

This library is a plugin for Next.js that automatically uploads your static assets to a specified CDN during build time and configures your Next.js application to use the specified CDN prefix. This makes it easy to set up and optimize your assets for better performance.

Currently, it supports Google Cloud Storage, but support is planned to other CDNs such as AWS S3, Cloudflare, and more in the future! 🌟

📦 Installation

Install the package using your favorite package manager:

npm install next-plugin-cdn

or

yarn add next-plugin-cdn

🔧 Usage

Set the appropriate environment variables for your project.

In your next.config.js, import the plugin and use it to configure your application:


// Import the plugin and pass cdn info and credentials
// for example using env vars:
const withCDN = require("next-plugin-cdn").default({
  domain: process.env.NODE_ENV === "production" && process.env.CDN_DOMAIN,
  provider: process.env.CDN_PROVIDER,
  bucket: process.env.CDN_BUCKET,
  keyFilename: process.env.CDN_KEY_FILENAME,
});


// Then just apply to your nextjs config
/** @type {import('next').NextConfig} */
const nextConfig = withCDN({
  output: "standalone",
  reactStrictMode: true,
  swcMinify: true,
  experimental: {
    appDir: true,
  },
});

module.exports = nextConfig;

Now, during the build process, the plugin will upload your static assets to the specified CDN and configure your Next.js application to use the CDN prefix. 🎉

⚙️ Options

The withCDN function accepts an object with the following properties:

domain: The domain of your CDN. This should be set to the value of the CDN_DOMAIN environment variable. provider: The CDN provider you are using (e.g., google, aws, cloudflare, etc.). This should be set to the value of the CDN_PROVIDER environment variable. bucket: The name of the bucket where your assets will be uploaded. This should be set to the value of the CDN_BUCKET environment variable. keyFilename: The name of the JSON key file used for authentication with the CDN provider. This should be set to the value of the CDN_KEY_FILENAME environment variable.

These options are passed to the plugin, which then takes care of uploading the assets and configuring the CDN prefix. 🛠️

🛣️ Roadmap

  • [ ] Google Cloud Storage support
  • [ ] AWS S3 support
  • [ ] Cloudflare support
  • [ ] Other CDNs support (let me know if others are interesting)

Stay tuned for more CDN provider support! 🚧

📄 License

MIT License