Skip to content

Commit 4b2c376

Browse files
authored
Apply suggestion from @maartenba
1 parent 8fcaff2 commit 4b2c376

File tree

1 file changed

+2
-4
lines changed
  • src/content/docs/bff/fundamentals/multi-frontend

1 file changed

+2
-4
lines changed

src/content/docs/bff/fundamentals/multi-frontend/index.mdx

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -179,14 +179,12 @@ var frontend = new BffFrontend(BffFrontendName.Parse("frontend1"))
179179
When you do this, the BFF automatically wires up a catch-all route that serves the `index.html` for that specific frontend.
180180
See [Serve the index page from the BFF host](/bff/architecture/ui-hosting.md#serve-the-index-page-from-the-bff-host) for more information.
181181

182-
### Proxying all static assets
182+
### Proxying All Static Assets
183183

184-
When developing a SPA based application, it's very common to use a development webserver such as Vite. While vite can publish static assets with a 'base',
185-
this doesn't work well during development.
184+
When developing a Single-Page Application (SPA), it's very common to use a development webserver such as Vite. While Vite can publish static assets with a base URL, this doesn't work well during development.
186185

187186
The best development experience can be achieved by configuring the BFF to proxy all static assets from the development server:
188187

189-
190188
```csharp
191189
var frontend = new BffFrontend(BffFrontendName.Parse("frontend1"))
192190
.WithProxiedStaticAssets(new Uri("https://localhost:3000")); // https://localhost:3000 would be the URL of your development web server.

0 commit comments

Comments
 (0)