v1.9.0 — a theme's 'dev' script, and Vite behind a wrapper

The theme daemon was keyed on a start script in package.json. A repo that had renamed it to dev got no daemon at all — ddev rdg-sync said "no 'start' script, not configuring the theme daemon" and the site came up with assets that never rebuild.

ddev rdg-sync now takes the dev script if there is one and start otherwise, and writes the name it chose into the generated command::

command: "bash /mnt/ddev_config/rdg/theme-watch.sh dev"

dev wins when a repo declares both, because such a repo is mid-migration onto the newer toolchain.

Vite detection no longer requires Vite to be a direct dependency. A script that names vite counts too. Themes that get it through a wrapper (rdg-vite is ours) list no vite of their own, and were handed 35729 while their dev server listened on 5173 — the port exposed, nothing answering on it.

Upgrading

Run ddev rdg-sync after taking this release, then commit. Nothing changes until you do: DDEV never re-derives on an add-on upgrade, and theme-watch.sh defaults to start so an older generated config keeps working untouched.

One derived value may move when you re-sync: a theme whose script runs Vite without depending on it directly changes 35729 → 5173. Read the diff before committing it.

Vite themes: allow the DDEV host

Vite refuses a host it does not recognise, with a 403 that reads as a routing fault:

Blocked request. This host ("rdg2020-vite.ddev.site") is not allowed.

Our shared config still pins the dkr-era allowedHosts: ['vite', 'localhost']. Under DDEV the host is <project>.ddev.site — and since v1.8.1 that follows the directory, so it varies per checkout. Allow the suffix:

server: { allowedHosts: ['.ddev.site'] }

227 tests, up from 220.

Full changelog: v1.8.1...v1.9.0