Skip to content

Update deployment documentation for JavaScript apps #643

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
IEvangelist merged 2 commits into from
Mar 31, 2026
+4 −4
Merged

Update deployment documentation for JavaScript apps #643

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1865fa2
Update deployment documentation for JavaScript apps
DamianEdwards Mar 30, 2026
78a2720
Apply suggestions from code review
IEvangelist Mar 31, 2026
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
8 changes: 4 additions & 4 deletions src/frontend/src/content/docs/deployment/javascript-apps.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ For deployment, `AddViteApp` and `AddJavaScriptApp` should be treated as fronten
To deploy a JavaScript frontend, you must choose which other resource owns the public HTTP surface in production:

- Use `PublishWithContainerFiles(...)` when your backend or web server will serve the built frontend files.
- Use `PublishWithStaticFiles(...)` when your reverse proxy, gateway, or BFF will serve the built frontend files.
- Use `PublishWithStaticFiles(...)` when your reverse proxy, gateway, or <abbr title="Backend for Frontend">BFF</abbr> will serve the built frontend files.

If you only add a Vite or JavaScript app and reference backend services, Aspire still needs one of these production hosting patterns to know who serves the built frontend in deployment.

Expand Down Expand Up @@ -223,9 +223,9 @@ await builder.build().run();
</Tabs>

<Aside type="note">
`AddViteApp` is still fine in this model. The trap is not `AddViteApp` itself
— it is treating the Vite development server endpoint as a publish-time
dependency.
`AddViteApp` is still fine in this model but it's important to
understand that the Vite development server endpoint is not used at
publish-time.
</Aside>

### Dev-only gateway wiring
Expand Down