Closed smolattack closed 1 year ago
Hi @smolattack it looks like you are using the default SWA CLI port which is 4280
, so you would need to access your application on http://localhost:4280
, and not http://localhost:5173
.
@manekineko - Is it possible the CLI runtime could be improved to understand the issue and suggest the fix in the logs or in the response?
Hi @smolattack it looks like you are using the default SWA CLI port which is
4280
, so you would need to access your application onhttp://localhost:4280
, and nothttp://localhost:5173
.
There's noting on port 4280. I've pretty much given up on local dev and just publish my app for testing. I don't expect this to be fixed on Linux so I'm closing this.
Are you accessing the CLI from the default port
:4280
?--port
) and accessing the CLI from that port:4280
ℹ️ NOTE: Make sure to enable debug logs when running any
swa
commands using--verbose=silly
Describe the bug When locally developing, the api is not proxied which means you can't just call
fetch("api/whatever")
.Deploying the app and accessing it from the public URL, seems fine.
To Reproduce Steps to reproduce the behavior:
swa
and accept the defaultsswa start
orswa start --api-location api
Expected behavior Should be able to call api endpoints locally on the same socket as the client app.
Screenshots
Desktop (please complete the following information):
Additional context Add any other context about the problem here.