Interface TopViteConfig

Allows vite to handle custom import phrases, note if they're in tsconfig not 100% sure if this is needed. E.g. import { resolve } from "path"; alias: { "@": resolve("./bitbazaar"), }

Or better yet, just use the tsconfig paths:
import tsconfig from "./tsconfig.json";
alias: tsconfig.compilerOptions.paths,
Copy

Extra globs to exclude from traversal, can help with performance:

Include the inspect plugin, which allows you to see how vite is transforming code:

Proxy rules to apply to the dev server (i.e. when it should forward requests to a backend)

The os path to the files that will deployed to sameDomStaticUrl. Note if the static files are hosted on the same domain (i.e. not linking to a cdn, these can be the same as main static version) E.g. /.../~sds

The absolute url online that sameDomStaticPath files can be retrieved from Note if the static files are hosted on the same domain (i.e. not linking to a cdn, these can be the same as main static version) E.g. https://example.com/~sds

The os path to the files that will deployed to staticUrl. E.g. /.../static

The absolute url online that staticPath files can be retrieved from E.g. https://example.com/static