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: docs/activities/building-an-activity.mdx
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,7 +88,7 @@ npm install
88
88
npm run dev
89
89
```
90
90
91
-
If you visit http://localhost:3000/ you should see a vanilla JS frontend template running with [Vite](https://vitejs.dev/).
91
+
If you visit http://localhost:5173/ you should see a vanilla JS frontend template running with [Vite](https://vitejs.dev/).
92
92
93
93
While it's not much at the moment, in the following steps we'll connect it to the backend services, make it runnable in Discord, and power it up by populating it with data we pull from Discord APIs.
94
94
@@ -278,7 +278,7 @@ Your app should start and you should see output similar to the following:
278
278
```
279
279
VITE v5.0.12 ready in100 ms
280
280
281
-
➜ Local: http://localhost:3000/
281
+
➜ Local: http://localhost:5173/
282
282
➜ Network: use --host to expose
283
283
➜ press h + enter to show help
284
284
```
@@ -289,10 +289,10 @@ We'll use the Local URL as our publicly-accessible URL in the next step.
289
289
290
290
Next, we'll need to set up the public endpoint that serves the Activity's frontend. To do that, we'll create a tunnel with a reverse proxy. While we'll be using [`cloudflared`](https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/) in this guide, you can use [ngrok](https://ngrok.com/docs) or another reverse proxy solution if you prefer.
291
291
292
-
While your app is still running, open another terminal window and start a network tunnel that listens to the port from the last step (in this case, port `3000`):
292
+
While your app is still running, open another terminal window and start a network tunnel that listens to the port from the last step (in this case, port `5173`):
293
293
294
294
```
295
-
cloudflared tunnel --url http://localhost:3000
295
+
cloudflared tunnel --url http://localhost:5173
296
296
```
297
297
298
298
When you run `cloudflared`, the tunnel will generate a public URL and you'll see output similar to the following:
0 commit comments