v1.5.0

Highlights

This release adds a "Manifest Mode (No Dev Server)" section to references/vite-configuration.md, covering build-time-only asset workflows where vite build runs at install or image-build time and no HMR server ever exists. It documents three production traps verified end-to-end on a TYPO3 v14 reference stack: the useDevServer = auto default resolves to Environment::getContext()->isDevelopment(), so any Development/* context silently chases a dev server that is not running; ExtensionConfiguration::get() with a key missing from a sealed read-only settings.php triggers a write attempt that throws core exception #1346323822 and turns the frontend into an HTTP 500; and vite-plugin-typo3 project-mode output aligns with the extension's defaultManifest by design, so <vite:asset> needs no manifest argument.

Added

• "Manifest Mode (No Dev Server)" section in references/vite-configuration.md (#10): forcing useDevServer = '0', pre-populating the complete vite_asset_collector key set in settings.php, and the defaultManifest alignment rationale
• Deployment note: keep package.json and vite.config.js at the Composer project root so node_modules never sits inside copied extension paths

Changed

• .markdownlint-cli2.jsonc is now committed with the same defaults the reusable validate workflow generates, restoring local-hook/CI parity (no CI behavior change)

Full Changelog: v1.4.0...v1.5.0