Troubleshooting

Check the installed version

1npm ls @qentrah/cms

Compare the installed version with the version noted in this guide. Inspect your lockfile before changing dependencies; prerelease behavior may differ between versions.

Import or module errors

Use only public import paths listed in API and exports. Avoid importing guessed paths inside dist. ESM-only packages require an ESM-aware application. Install declared peer dependencies in the consuming application.

Application starts but persistence fails

Check the configured runtime provider and database bindings before making content requests. The app factory does not provision credentials or schema. Use the consuming application’s documented migrations. Do not use the qentrah-db-reset command as a generic recovery step: it resets data.

Plugin routes are missing

Register plugins explicitly with plugins.register. The directory and autoLoad fields are deprecated no-ops; a Worker does not have a filesystem to scan.