You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: readme.md
+26-8Lines changed: 26 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,6 +53,24 @@ Using `npx`:
53
53
- Start the emulator: `npx @manekinekko/swa-emu@latest`
54
54
- Access your SWA app from `http://localhost`
55
55
56
+
### Start the emulator from a specific folder
57
+
58
+
By default, SWA EMU will start from the current directory `./`. But if you have multiple SWA projects, you can start SWA EMU with a specific folder, and the emulator will use that folder as the `app_location`.
59
+
60
+
If your SWA project is under `./my-app`, then run the SWA EMU and provide that folder:
61
+
62
+
```bash
63
+
swa ./my-app
64
+
```
65
+
66
+
> Please also note, that running `swa ./my-app` is equivalent to `swa --app-location=./my-app`.
67
+
68
+
In case the SWA EMU cannot determine the right frontend application artifact (dist) folder to serve, you can override this configuration by providing the `--app-artifact-location` flag:
When developing locally on your back-end application, it might be useful to use your local API dev server, to serve your API content and benefit from the built-in features like debugging. In order to use SWA EMU with your local API dev server, follow these two steps:
0 commit comments