Deployment

Shipping Guchho's output to a static host.

Guchho produces an output directory (dist by default) that can be uploaded to any static host. There is no server-side component.

Absolute URLs

publicPath prefixes asset URLs in the output, for a build served from a sub-path or a CDN:

build: { publicPath: 'https://cdn.example.com/assets/' }

Give output names a content hash so a deploy invalidates caches only for the files that changed:

build: {
  entryNames: '[name]-[hash]',
  chunkNames: 'chunks/[name]-[hash]',
  assetNames: 'assets/[name]-[hash]',
}

Guchho rewrites every URL that points at a renamed file, so the HTML keeps working without manual edits.

For production, linked or external maps keep the .map files out of the bundle while staying fetchable:

build: { sourcemap: 'linked', sourcesContent: 'exclude' }

A typical CI step:

npm ci
npx guchho build --preset production

There is no --preset in Guchho itself; use a config file plus a build script per environment, or pass flags directly:

guchho build --outdir=dist --minify --sourcemap

guchho pack dist -o release.zip