https://discord.cloudflare.com logo
Join Discord
Powered by
# functions
  • d
    I use Hugo. Hugo exports its static site into a "public" directory. So in my project's root folder, i have a /public and a /functions subfolders.
  • d
    yes. my 
    functions
    folder is inside my project's root folder where I run the command. but it doesn't seem to serve the function
  • d
    Anyone could increase function requests limit? I've filled up the form but no joy 🙂
  • e
    Someone should have a look at that and make the change @User..
  • g
    Do you have a repo I can look at?
  • b
    Im having issues trying to get wrangler pages dev to server my local directory. The directory only contains a functions fodler with a [[slug]].js to handle all routes. The command im running is: 
    npx wrangler@beta pages dev ./ --proxy 8000 --kv SECOND_KV_NAMESPACE
    and my server started with from the project root directory: 
    python3 -m http.server 8000
    Im getting a 404 on all pages, is it supposed to work on this setup?
  • g
    You likely don’t need the proxy pieces there.
  • g
    If you’re just trying to serve a static folder, you can just 
    npx wrangler pages dev ./that-folder
  • g
    No need for the Python command
  • b
    @User Thanks, but I still get a 404. Calling this from the root of my project. 
    npx wrangler@beta pages dev ./ --kv KV_NAMESPACE_NAME
  • g
    Do you have a repo you can share?
  • b
    Yea, sure can. Should I just DM you?
  • g
    Can do!
  • d
    Hi @User , after checking the compiled worker 
    functionsWorker.js
    created by the pages dev command, i found that the routePath was not properly escaped,.?
  • d
    this is the structure of my functions directory: - functions/api/collection - functions/api/tokens but routes.routePath in the compiled 
    functionsWorker.js
    were 
    "/apicollection"
    and 
    "/api    okens"
    ps. i'm using Windows
  • g
  • j
    How do I view logs for functions? I'm getting an error saying my worker threw an exception and to check logs, but i'm not seeing anywhere to view them
  • o
    You can't right now. I think I've seen recommendations to send logs to a 3rd party service like Sentry (if you can't reproduce the error locally)
  • g
    npx wrangler@beta pages dev --help
    if you want to try reproducing locally.
  • g
    We’ll get production logs in place for GA
  • w
    Hi there, anyone could help me on how to add environment variables in functions on local development?
  • w
    I've tried the .toml file with no success
  • g
    npx wrangler pages dev ./static_assets_dir --binding ENV_VAR_NAME=VALUE
  • w
    That's great! but what if I've a long list? is there a way to point to a 
    .env
    file or something similar?
  • w
    I could definitely build my way around it but wonder if there's a cleaner solution like when you pass the 
    .toml
    config file with the 
    --config
    flag
  • w
    for anyone who might be looking for a cleaner way to get your long list of env variables available on local development this was the best solution I've found: 
    npx wrangler pages dev --binding $(cat .env) -- npm run dev
  • w
    this way you can still store all your env vars under your 
    .env
    file
  • g
    Not currently. There are some issues up on the wrangler repo tracking this, but they haven’t yet been implemented.
  • b
    I have a question about _worker.js (pages->functions->_worker.js ) does it work on 
    wrangler pages dev
    environment? I have not gotten it to work successfully.
  • g
    _worker.js
    should be placed in your static assets folder for it to be picked up
1...565758...392Latest