Launchready Frontend CDN is now generally available as a free China Frontend CDN — a Mainland China–reachable Alibaba Cloud CDN mirror of curated npm libraries when jsDelivr, BootstrapCDN, or ajax.googleapis.com are slow or unreliable. It keeps familiar jsDelivr-shaped /npm/ paths and ajax.googleapis-shaped /ajax/ paths on fd-cdn.launchready.cn, without changing upstream licenses.
When jsDelivr and BootstrapCDN stall in China
A page can look fine from an overseas monitor while Bootstrap, jQuery, Vue, React, or another CDN-hosted script never finishes loading for users in Mainland China. jsDelivr China reach, BootstrapCDN, and Google Hosted Libraries (ajax.googleapis.com) are common third-party origins on that critical path. When they stall, the HTML may still return 200 while the product shell stalls. Teams often compare domestic options such as Staticfile CDN or BootCDN; the Chinaready Landscape alternatives index — including BootstrapCDN — maps the same dependency class when you inventory what to remap onto a China CDN.
Moving those library files onto a Mainland China–reachable CDN hop removes one external request chain. It does not, by itself, make the rest of a product ready for Mainland China. Fonts, APIs, authentication, media, analytics, and other services still need to be tested as part of the actual stack.
After Chinaready published Google Fonts as a free WOFF2 mirror for Mainland China — covered in GFonts is GA for Mainland China — the utility drew strong attention from teams hitting the same third-party origin problem. Frontend CDN continues that line of free infrastructure work for the npm and Ajax hosts teams actually pin in production, so more China-facing projects can keep a familiar library path without depending on overseas CDNs that fail for ordinary users.
What general availability includes
Frontend CDN publishes a curated snapshot of OSI-licensed or freely redistributable packages — frameworks, UI helpers, dates, charts, media, and related libraries — with one latest stable patch retained per selected major. The live inventory is also published in manifest.json.
Current published package versions:
| Package | Version |
|---|---|
| bootstrap | 4.6.2 |
| bootstrap | 5.3.8 |
| @popperjs/core | 2.11.8 |
| jquery | 3.7.1 |
| vue | 2.7.16 |
| vue | 3.5.41 |
| react | 18.3.1 |
| react | 19.2.8 |
| react-dom | 18.3.1 |
| react-dom | 19.2.8 |
| axios | 1.19.0 |
| lodash | 4.18.1 |
| @fortawesome/fontawesome-free | 6.7.2 |
| bootstrap-icons | 1.13.1 |
| echarts | 5.6.0 |
| chart.js | 4.5.1 |
| three | 0.185.1 |
| leaflet | 1.9.4 |
| video.js | 8.24.0 |
| swiper | 11.2.10 |
| dayjs | 1.11.23 |
| moment | 2.30.1 |
| highlight.js | 11.12.0 |
| sweetalert2 | 11.26.25 |
| hls.js | 1.7.1 |
| sortablejs | 1.15.7 |
| animejs | 3.2.2 |
If the package or version you plan to use is not listed here, contact us to request it. Chinaready will review licensing and arrange to add the needed release as soon as practical.
Two path shapes are supported after an Origin is allowlisted:
- npm / jsDelivr shape — for example
https://fd-cdn.launchready.cn/npm/[email protected]/dist/jquery.min.js - Ajax / ajax.googleapis shape — for example
https://fd-cdn.launchready.cn/ajax/libs/jquery/3.7.1/jquery.min.js
Cross-origin use is restricted to allowlisted Origins. A site cannot point at the mirror from an arbitrary domain and assume the files will load. The Frontend CDN allowlist is separate from the GFonts allowlist — approval on one product does not automatically grant the other. Adding a domain requires an application through the Contact form, listing every production and staging Origin.
The mirror also leaves every upstream package license unchanged. Chinaready does not relicense the libraries or grant additional commercial rights. Teams remain responsible for reviewing and following the original license for each selected package.
General availability means the utility, documented usage path, current corpus, and operating controls are in place. It does not mean that every npm package is mirrored, that every historical version is retained, that every Origin is accepted, or that the service changes the legal terms of an upstream library.
How to replace a jsDelivr or Ajax CDN link
Pin the exact published version from the manifest. Package contents keep their upstream filenames and licenses.
On an allowlisted site, replace the overseas CDN reference with the corresponding Launchready path. For jQuery 3.7.1:
<script src="https://fd-cdn.launchready.cn/npm/[email protected]/dist/jquery.min.js"></script>Or the Ajax-compatible alias:
<script src="https://fd-cdn.launchready.cn/ajax/libs/jquery/3.7.1/jquery.min.js"></script>Before changing a production site, confirm that the intended package and version are present in the manifest, that the site’s Origin is allowlisted, and that the page still degrades acceptably if a script request fails.
Teams should also test the page from Mainland China after the change. A successful library request is useful evidence, but page-level checks are still needed for rendering, layout stability, caching, and the other dependencies loaded alongside the script.
A free utility, not a full readiness verdict
Frontend CDN is a free Chinaready infrastructure utility under launchready.cn. It addresses one concrete dependency class — overseas frontend CDN / npm hosts — and gives teams a direct way to remove jsDelivr, BootstrapCDN-class, or ajax.googleapis delivery from a Mainland China user journey.
It is not a paid service SKU, and using it does not replace a broader review of a website, platform, or app. If library delivery is only one of several uncertain dependencies, the China Readiness Assessment maps the stack, tests the relevant failure points, and recommends which route is worth considering. For self-serve mapping of other global tools, start with the Landscape alternatives index.
Open Frontend CDN to review the live corpus, usage instructions, and service boundaries — then apply for free use with every Origin that must load the files.
