StencilJS production build omits lazy-loaded chunks referenced in chunk manifest

Goal

Achieve a reliable production deployment where all lazy-loaded components defined in the StencilJS chunk manifest are emitted and load correctly at runtime.

Constraints and uncertainty

The compiler's static analysis cannot resolve dynamic import expressions that use variables (for example import("./components/" + name)), so those chunks are not emitted in a production build even though the development server compiles them on demand. The generated stencil-chunk-manifest.json still references the missing chunks, causing 404 errors when the hydration script requests them. Output target configuration adds another variable: the www target uses content-hashed filenames while dist-custom-elements uses deterministic names, so mixing targets without aligned basePath and buildDir settings produces manifest mismatches. Stencil v4's migration to Vite also changed the chunk generation pipeline, and legacy Rollup plugins may emit manifests that the new runtime cannot consume.

Questions

1. What is the recommended pattern to enumerate every lazy-loaded component so the static analyzer emits all required chunks?
2. How should basePath and buildDir be coordinated across multiple outputTargets to guarantee a single, consistent manifest at deploy time?
3. Are there version-pinning or migration steps that prevent legacy Rollup plugins from producing manifests incompatible with the Vite-based runtime?