https://discord.cloudflare.com logo
Join Discord
Powered by
# functions
  • w
    Does anybody know what this error is: “This readable stream is currently locked to a reader”
  • w
    @User so I ended up getting stuck, your initial code gave this error: “text: '"await" can only be used inside an "async" function” So I tried making it asynchronous only to get this “This readable stream is currently locked to a reader” which I had not seen before and which is basically not coming up in Google. https://github.com/datapolitical/chrisfnicholson.github.io/blob/cloudflare-functions/functions/index.js
  • w
    If anybody else wants to take a look I really appreciate it
  • g
    Ah, sorry, just add the 
    async
    keyword when defining the function
  • g
    export const onRequestGet = async ({ request, next }) => {
  • w
    That makes sense given the error. I should’ve just done exactly what it said. Out of curiosity, how is that syntax different than the one at the top of the weather example
  • w
    export async function onRequest(context) { try { // Contents of context object const { request, // same as existing Worker API env, // same as existing Worker API params, // if filename includes [id] or [[path]] waitUntil, // same as ctx.waitUntil in existing Worker API next, // used for middleware or to fetch assets data, // arbitrary space for passing data between middlewares } = context;
  • w
    Like it seems to be doing something similar but not exactly the same
  • k
    That is if you use the cache api on a function/worker
  • i
    Am I correct in saying that 
    @sveltejs/adapter-cloudflare
    for cloudflare pages generates a 
    _worker.js
    file, which means every page request is caught by the worker and counts towards my function requests which will eventually be billed?
  • k
    afaik, yes
  • i
    Yes. Note that, as was said above, currently every method to add functions boils down to creating the 
    _worker.js
    file, so it’s the same behaviour regardless.
  • i
    Ahh I see, thanks!
  • g
    onRequestGet
    will only respond to GET requests whereas 
    onRequest
    will respond to all requests. Rest of it is just down to personal preference though. Should be functionally identical.
  • w
    That’s what I was hoping you would say
  • w
    And the whole idea behind Wrangler is that instead of building the preview every 10 minutes to test a change I’ll be able to just test it locally, right
  • w
    And it looks like there’s a local mode as well, does the non-local mode count as a build?
  • k
    i imagine so
  • g
    There is no non-local 
    wrangler pages dev
    at the moment.
  • g
    We’re still thinking about it. What would you expect 
    npx wrangler pages dev --remote
    to do?
  • k
    just to be clear, it's local only atm, right?
  • g
    Yes.
  • w
    https://blog.cloudflare.com/wrangler-v2-beta/ so this talks about having a local mode which is why I was confused because I thought the whole point was that it was local
  • w
    @User i’m sure there’s something I’m just not understanding because I’m new to all this
  • g
    wrangler pages dev
    is entirely local. No builds are used when you’re testing with 
    wrangler pages dev
    . Wrangler let’s you test Workers locally or remotely. We don’t have a remote equivalent for Pages yet. I was just wondering what you thought a remote version might look like. No biggie if you don’t have any thoughts on that. I was just curious 😊
  • w
    I guess a more controlled way to test how things behaved at the edge, especially if it didn’t require you to rebuild your entire site
  • w
    Like when dealing with Jekyll, there were always things that wouldn’t show up as a problem if you tested the site locally, but when you built it on the server other problems would come up
  • w
    And like, building a preview of my site takes 10 minutes, so I can imagine finding a way to have perhaps continuous local rebuilding that gets pushed up to the network would be really cool.
  • w
    And being able to put it up on your servers lets other people look at it as well while I’m working on it, without having to do a full preview rebuild.
  • k
    That's what preview builds are for
1...111213...392Latest