Adding CDN Caching to a Vite Build
Leveraging a Content Delivery Network (CDN) significantly enhances website performance by caching static assets closer to users. CDNs achieve this by distributing content across globally dispersed edge servers. When a user accesses your site, the CDN directs the request to the nearest server. If the asset is already cached (from a previous visit or another user), it's served instantly. Otherwise, the CDN fetches it from your origin server, caches it, and then delivers it.
This tutorial uses AWS CloudFront as an example, demonstrating how to configure a distribution to serve JavaScript, CSS, font files, and other static assets, and integrate it with a Vite build process. For a more robust approach, consider using infrastructure-as-code tools like the Serverless Framework or AWS CDK. However, for simplicity, we'll use the AWS console.
Configuring an AWS CloudFront Distribution
- Navigate to the CloudFront homepage in the AWS console.
- Click the "Create Distribution" button.
- In the creation screen, specify the origin domain (where your assets reside). Most default settings are suitable.
- Crucially, select "CORS-With-Preflight" from the "Response headers policy" dropdown.
- Click "Create Distribution." Your new distribution will then appear.
Integrating CloudFront with Vite
While setting up the CDN is essential, your website must be configured to retrieve assets from it. This integration is similar across various build systems (Webpack, Rollup, etc.).
- In your
vite.config.ts
file, determine if the build is for production:
const isProduction = process.env.NODE_ENV === "production";
- Configure Vite to use the CDN in production:
export default defineConfig({ base: isProduction ? process.env.REACT_CDN : "", });
Remember to set the REACT_CDN
environment variable to your CloudFront distribution's URL (e.g., https://distributiondomainname.cloudfront.net
).
VitePWA Compatibility
If using the VitePWA plugin, ensure your base
property is correctly set:
VitePWA({ base: "/", });
Incorrect settings can lead to errors in your web.manifest
file.
Verifying CDN Functionality
After setup, inspect network requests for your site's assets. You should observe the h2
protocol. Examine the response headers; you'll find CloudFront-related data confirming the CDN's involvement.
Cache Busting with Vite
Vite automatically handles cache busting through fingerprinting. It adds hash codes to asset filenames (e.g., home-abc123.js
). When assets change, the hash changes, forcing the CDN to fetch the updated version.
Extending CDN Caching
CDN caching benefits extend beyond JavaScript, CSS, and fonts. If using S3 for image storage, consider configuring a CloudFront distribution for it. This not only provides edge caching but also enables HTTP/2 support, which S3 lacks.
Advanced CDN Strategies
This tutorial covers basic CDN integration. For optimal performance, consider serving your entire site from the CDN, allowing it to interact with your origin server only for dynamic content.
Conclusion
CDNs are a powerful tool for enhancing website performance by providing edge caching and HTTP/2 support. This guide simplifies the process of setting up a CDN and integrating it with Vite, equipping you with a valuable performance optimization technique.
The above is the detailed content of Adding CDN Caching to a Vite Build. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

It's out! Congrats to the Vue team for getting it done, I know it was a massive effort and a long time coming. All new docs, as well.

I'd say "website" fits better than "mobile app" but I like this framing from Max Lynch:

I had someone write in with this very legit question. Lea just blogged about how you can get valid CSS properties themselves from the browser. That's like this.

If we need to show documentation to the user directly in the WordPress editor, what is the best way to do it?

The other day, I spotted this particularly lovely bit from Corey Ginnivan’s website where a collection of cards stack on top of one another as you scroll.

There are a number of these desktop apps where the goal is showing your site at different dimensions all at the same time. So you can, for example, be writing

CSS Grid is a collection of properties designed to make layout easier than it’s ever been. Like anything, there's a bit of a learning curve, but Grid is

I see Google Fonts rolled out a new design (Tweet). Compared to the last big redesign, this feels much more iterative. I can barely tell the difference
