Skip to content

Add resource-fallback — zero-intrusion asset fallback plugin#8266

Closed
ben-lau wants to merge 1 commit into
webpack:mainfrom
ben-lau:patch-1
Closed

Add resource-fallback — zero-intrusion asset fallback plugin#8266
ben-lau wants to merge 1 commit into
webpack:mainfrom
ben-lau:patch-1

Conversation

@ben-lau

@ben-lau ben-lau commented Jun 15, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds resource-fallback — a runtime resource fallback solution for frontend build outputs (Vite & Webpack).

What it does

When a CDN or static asset URL fails at runtime, resource-fallback automatically:

retry → switch to backup CDN → fall back to origin

…without requiring changes to application code. Works with sync/async JS, CSS chunks, React.lazy, Vue defineAsyncComponent, Vue Router lazy routes, and more.

Why it fits this list

How it differs from similar tools

This is not a build-time CDN import plugin (e.g. swapping React/Vue to a CDN at compile time).

It targets a different problem: your own build artifacts (entry bundles, async chunks, CSS) failing to load in the browser due to CDN/network issues — with a unified retry + multi-source fallback strategy.

Compared to Webpack-only retry plugins, it also covers Vite, DOM <script>/<link> error handling, optional Hybrid Service Worker for images/fonts/CSS url(), per-host circuit breaker, kill switches, and CSP/SRI compatibility.

Links

README change

See diff — one line under [CATEGORY].

Added a new plugin for runtime retry and multi-CDN fallback.
@vercel

vercel Bot commented Jun 15, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
webpack-js-org Ready Ready Preview, Comment Jun 15, 2026 11:58am

Request Review

@github-actions

Copy link
Copy Markdown

👋 Hi there! This PR was automatically flagged and closed by our quality checks.

If you believe this was a mistake, please review our contributing guidelines
and leave a comment explaining why this is a mistake.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant