https://discord.cloudflare.com logo
Join Discord
Powered by
# functions
  • s
    5173 is vite's port - you'll need to visit the one wrangler opens instead
  • s
    Visiting the correct port logs "Hello world!" each time I click the button
  • y
    I know, kian has told me that. Do I have to 
    fetch
    the wrangler's host and set up CORS on the client side, which is unnecessary in production? That doesn't sound very practical...
  • s
    Not sure why you'd need any of that? Seems to be functioning fine
  • s
  • y
    Ah didn't notice visiting :8788 leads to the app, thanks! how stupid of me 🤦
  • y
    I thought that port was only for functions.
  • s
    Wrangler will take that port, serve your functions, and anything that isn't a function gets proxied to the port of the command that it ran, in this case it ran 
    vite
    , so it proxies 5173
  • s
    Meaning you never have to visit vite's one directly
  • y
    Got it. Maybe can it be documented at https://developers.cloudflare.com/pages/platform/functions/local-development/ if I'm not the only one who makes this silly mistake?
  • s
    I've not personally seen anyone have this - but if you'd like it to be documented, making an issue on the docs repo is the best way 🙂
  • d
    @Erisa | Support Engineer sorry stupid question, can I store the port number in a config file somewhere?
    Copy code
    wrangler pages dev --proxy 57985 -- vite
  • s
    Unfortunately not currently
  • s
    I'd recommend you take advantage of the package.json scripts for this, so you can have a shortcut like "npm run dev"
  • d
    ty for confirming, that's what I was bout to do
  • c
    "Writing your Functions files in this directory will automatically generate a Worker with custom functionality at predesignated routes" What if the route is dynamic like: https://domain.com/creator/ {username} /
  • c
    Each user has their own main page. That needs to be generated.
  • c
    Found it
  • w
    /functions/creator/[username].ts
  • c
    Functions are a life saver.
  • e
    Functions are pretty great
  • c
    Is there any way to get error like with workers?
  • c
    error logs or something
  • w
    yep you can tail just like Workers: * Dash: * Wrangler: 
    wrangler pages deployment tail
  • c
    thanks
  • h
    Hello, am i able to run my pages function on every url route ?
  • w
    funtions/[[path]].js
    runs on all paths 🙂
  • h
    amazing!!
  • h
    is that in the documentation somewhere ?
  • w
1...331332333...392Latest