Tobias Laundal

> I may be misunderstanding, but I think you can do that by running `npm run build` and using the [current configuration in the README](https://github.com/geoffrich/svelte-adapter-azure-swa#running-locally-with-the-azure-swa-cli). It points `swa` at the...

> @tlaundal I've been developing a SWA + Svelte project recently, I was able to get frontend & backend working by passing the Svelte address as the API dev server...

I just solved the above issue, and it seems to be a bug in `swa`. What happens is that `swa` tries to make connections to `localhost:7071`, while azure functions core...

Here's another caveat to keep in mind about `swa`, it doesn't support pre-generated routes very well, as it hasn't implemented support for rewriting `/my/route` to `/my/route.html`. See Azure/static-web-apps-cli#418

> Yep, confirmed in #113 that is the case. So if we wanted to make that switch, we'd have to add routing rules for anything in `static` and any prerendered...

I think this is blocked by Azure/azure-functions-host#1361. I spun up a function just to test if it was somehow supported, but couldn't find a way to return a stream.