This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-12-13
Channels
- # adventofcode (37)
- # announcements (11)
- # babashka (46)
- # beginners (35)
- # biff (1)
- # clojure (44)
- # clojure-austin (1)
- # clojure-europe (23)
- # clojure-nl (2)
- # clojure-norway (8)
- # clojure-uk (5)
- # conjure (3)
- # cursive (22)
- # data-science (13)
- # docker (11)
- # events (8)
- # hyperfiddle (7)
- # joyride (1)
- # juxt (9)
- # malli (7)
- # matrix (4)
- # pedestal (3)
- # podcasts-discuss (1)
- # portal (1)
- # re-frame (62)
- # reitit (2)
- # releases (1)
- # schema (3)
- # sql (14)
- # squint (3)
- # xtdb (6)
- # yamlscript (4)
i have a pure frontend webpage that use reitit.frontend to do the routing. if i start from the root page (index.html) and click a link /xxx i can be brought to http://localhost:8080/xxx . if i refresh, i can still see the correct content. why does this work? my app.js is put in the <head> of index.html, so it should not be loaded when i directly visit http://localhost:8080/xxx ? if i put my index.html and my app.js to vercel.app. i can go to mysite.vercel.app and then mysite.vercel.app/xxx from that page. but if i refresh from mysite.vercel.app/ , i will have a 404 error. any idea why refreshing from /xxx in localhost works while hosting on web doesn't. thanks for your help~
turns out this is related to vercel itself not reitit: https://stackoverflow.com/questions/64815012/why-does-react-router-not-works-at-vercel can solve the issue