Why do I need @cloudflare/vite-plugin for an SPA?

[waynesbrain]

Before I integrate a new layer of code into my already byzantine React/SPA infrastructure I'd like to find out why I really need to use @cloudflare/vite-plugin. The features list says:

1. Integrates Vite Environment API with Workers runtime (to define Vite Env from wrangler config).
2. Provides direct access to Worker runtime APIs and bindings (not needed for SPA).
3. Builds your front-end assets for deployment to Cloudflare, enabling you to build static sites, SPAs, and full-stack applications (not sure why I need this, Vite was already doing a good job building a bunch of static stuff to deploy to Cloudflare).
4. Supports React Router v7 for SSR (not needed for SPA).
5. Leverages Vite's hot module replacement for consistently fast updates (when? At development time only hopefully? I already get hot module replacement directly from Vite and it's fast...)
6. Supports vite preview for previewing your build output in the Workers runtime prior to deployment (but I already get vite preview to run my SPA directly from vite...)

For item 3. I looked at the vite-plugin's Static Assets page and the main feature that I see is auto-configuration of asset binding. I'd much prefer to do this manually.

It looks like most of these features are for SSR and the features needed for SPA basically amount to auto-configuration of some things, which I don't like because I'd prefer explicit configuration. Am I missing something?