Ensuring deterministic build outputs in Qwik v1.5

Build Reproducibility in Qwik

Maintaining a repeatable development environment requires that the production build process produces identical artifacts regardless of the machine or OS performing the build. In Qwik v1.5, the build pipeline utilizes Vite and a specialized optimizer that performs symbol mangling to reduce bundle sizes.

There is uncertainty regarding whether the optimizer uses a deterministic seed for this mangling or if the order of module resolution affects the final output. Additionally, Qwik City's route generation relies on filesystem scanning, which may vary based on the underlying operating system's file listing order.

What configuration options exist to enforce a fully deterministic build? Does the current optimizer support a seed to prevent non-deterministic symbol mangling across different CI agents?