When Vite projects go wrong, the problem is often not a generic syntax issue. It is usually a mismatch with one of Vite's runtime contracts:

• a config file exports the wrong shape
• a client bundle relies on dynamic import.meta.env access
• a workspace mixes test and benchmark APIs in ways that make results harder to trust
• a server option disables a protection that Vite enables by default

That is why eslint-plugin-vite is intentionally centered on config safety and workspace correctness.

eslint-plugin-vite now has a clearer baseline for the things maintainers and users touch first: branding assets, docs navigation, ADRs, charts, and repository-wide validation.

That baseline work matters because the project is no longer a generic plugin template. The site, manifest, and docs structure need to communicate that this package is about Vite config safety, client-runtime correctness, and Vitest workspace discipline.