CDN Support

Is there any hope of this ever working with CDNs? Sometimes it seems the entire webpack ecosystem is built in a world where CDNs aren’t a thing…

If the generated index.html has absolute links for use with a CDN, say, the HTML is served from www.example.com and the assets are served from static.example.com, pre-rendering will fail because the assets are not actually on the CDN yet during the build process. You’d have to pre-render after deploying, so you’d end up with a two-stage deployment. Perhaps a separate build target that uses relative URLs instead of the CDN ones so that everything is available during build?

Is there a solution I’m overlooking?

[drewlustro]

A 2-step deploy is not uncommon.

At some point, we all have to write some code instead of assuming that there will be a plugin (or option for said plugin) to handle every project need.

Why not create a new task like npm run prebuild that creates all of your assets and uploads them to static.example.com as a prerequisite to npm run build?

package.json (hypothetical snippet)

{
  "private": true,
  "scripts": {
    "dev": "node build/dev-server.js",
    "prebuild": "node build/prebuild.js && rsync -r dist/static/* example.com:/sites/example/static",
    "build": "npm run prebuild && node build/build.js",
  }
}

[dhgan]

@krestaino You can look at this. prerender-cdn-demo