Skip to content

docs: document Vite CDN --base injection in build configuration #1626

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
parteeksingh24 merged 1 commit into from
Jul 23, 2026
Merged

docs: document Vite CDN --base injection in build configuration #1626

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/src/web/content/reference/cli/build-configuration.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -221,6 +221,8 @@ export default defineConfig({
});
```

On cloud deploy, Agentuity uploads hashed Vite assets to the CDN. The Vite adapter injects `--base=<cdn-origin>/` into the segment of your build command that runs `vite` when a deployment id or `AGENTUITY_CDN_ORIGIN` is available, so chunk URLs point at the CDN instead of the app origin. Local builds and `agentuity deploy --pack-only` skip this when no CDN origin can be resolved. If the build command does not invoke `vite`, the CLI cannot inject `--base` and asset URLs may stay on the app origin.

<Callout type="warning" title="Public env vars are browser-visible">
Values exposed through Vite public prefixes are bundled into frontend code. Do not put secrets or API keys in public variables.
</Callout>
Expand Down
Loading