i have to add type definitions or it manually or? did not mean to ping&*

B

bun•3/24/24, 10:57 PM

@HardlyWorkin' since you can purge cache by url, cant you just make

bKv

bKv

bKv

bKv cache indefinitely while purging on

.put

.put

.put

.put requests?

B

bun•3/24/24, 10:57 PM

only caveat is that you can only cache stuff by

caches.default

caches.default

caches.default

caches.default

Bbun @HardlyWorkin' since you can purge cache by url, cant you just make `bKv` cache ...

H

Hello, I’m Allie!•3/24/24, 10:58 PM

Maybe, but then you are limited to around 1k writes a minute(or whatever the limit is)

B

bun•3/24/24, 10:59 PM

also cache api only caches on the datacenter its called from right?

B

bun•3/24/24, 10:59 PM

like it doesnt replicate to other datacenters?

Bbun also cache api only caches on the datacenter its called from right?

H

Hello, I’m Allie!•3/24/24, 11:05 PM

Oh, you meant like that

H

Hello, I’m Allie!•3/24/24, 11:05 PM

You could do that too, but as you pointed out, it wouldn't propagate

B

bun•3/24/24, 11:06 PM

hm what did you mean then

B

bun•3/24/24, 11:06 PM

initially what u thought?*

Bbun hm what did you mean then

H

Hello, I’m Allie!•3/24/24, 11:06 PM

I thought you meant purging the Cache via

api.cloudflare.com

api.cloudflare.com

api.cloudflare.com

api.cloudflare.com

B

bun•3/24/24, 11:06 PM

yes, but the cache set from cache api

Bbun yes, but the cache set from cache api

H

Hello, I’m Allie!•3/24/24, 11:08 PM

That can still be cleared via the API, if that is what you mean?

B

bun•3/24/24, 11:09 PM

yes true

B

bun•3/24/24, 11:09 PM

idk what you thought otherwise

SSilent i have to add type definitions or it manually or? did not mean to ping&*

W

Walshy•3/24/24, 11:11 PM

yeah you'll want to declare a module like:

declare module '*.html' {
  const value: string;
  export default value
}

declare module '*.html' {
  const value: string;
  export default value
}

declare module '*.html' {
  const value: string;
  export default value
}

declare module '*.html' {
  const value: string;
  export default value
}

D

deleted_user_97ffca1b58d4•3/25/24, 1:59 AM

I have a project in which I have to have a WebSocket connection on 24/7, watching for a (rare) event. If that event happens, I need to run some code, then restart the WebSocket and watch for the event again.

Is Workers suitable for this? From my understanding, there's no limit on wall time, so this would be feasible as long as the total CPU time stays under 10ms

B

bun•3/25/24, 3:53 AM

why is ctx.cf.city available on pages but not in workers ?

W

Walshy•3/25/24, 5:07 AM

It's available in both - https://reqinfo.walshy.dev/

B

bun•3/25/24, 5:42 AM

yea its just hidden in

c.req.raw.cf

c.req.raw.cf

c.req.raw.cf

c.req.raw.cf for hono, mb

B

bun•3/25/24, 9:39 AM

Ok what if like cloudflare team works on less things but finish them instead of just having 100 things in beta? Like what? Probably wrong channel for this but i think it gets the most attention from cloudflare team so i hope anyone sees this

W

Walshy•3/25/24, 11:47 AM

Things that are in beta go GA when they're ready to.

I think you'd rather we call it beta than have a "production ready" product that isn't production ready.

N

Nick•3/25/24, 3:34 PM

Hey all

Have I just chosen the wrong tech by going with cloudflare workers? I just assumed I'd be using a node environment in my routes (astro ssr), and am trying to use either Mailgun or Sendgrid (with no luck because of 'define'/'fs' etc :D)

R

rob•3/25/24, 7:19 PM

Astro routes work on pages

M

Mozzy•3/25/24, 7:36 PM

I have a general cache question:
I am using Hono's cache middleware to set the cache:

cacheControl: "public, max-age=600"

cacheControl: "public, max-age=600"

cacheControl: "public, max-age=600"

cacheControl: "public, max-age=600"
When the endpoint is hit in Postman, it always returns

public, max-age=600

public, max-age=600

public, max-age=600

public, max-age=600 in the response headers.
When the endpoint is hit from a browser, it returns

public, max-age=14400

public, max-age=14400

public, max-age=14400

public, max-age=14400 in the response headers.

Having said that, it does seem like the browser does respect the 600 seconds. I'm wondering why it shows 14400

NNick Hey all 🙂 Have I just chosen the wrong tech by going with cloudflare workers? I...

A

alok•3/25/24, 8:12 PM

I'm using Sendgrid by hitting Sendgrid's API directly with a fetch. It works but I understand that using the node package is nicer/easier.

N

Nick•3/25/24, 8:13 PM

that's what i'm trying now... not much luck so far :/

NNick that's what i'm trying now... not much luck so far :/

A

alok•3/25/24, 8:14 PM

      const personalizations = [{
          to: [{ email: to }],
        }];
      const msg = {
      personalizations,
      from: {
        email: fromAddress,
        name: fromName,
      },
      subject: subject,
      content: [{ type: "text/plain", value: plainText }],
    };
    const email = await fetch("https://api.sendgrid.com/v3/mail/send", {
      body: JSON.stringify(msg),
      headers: {
        Authorization: `Bearer ${env.SENDGRID_API_KEY}`,
        "Content-Type": "application/json",
      },
      method: "POST",
    });

      const personalizations = [{
          to: [{ email: to }],
        }];
      const msg = {
      personalizations,
      from: {
        email: fromAddress,
        name: fromName,
      },
      subject: subject,
      content: [{ type: "text/plain", value: plainText }],
    };
    const email = await fetch("https://api.sendgrid.com/v3/mail/send", {
      body: JSON.stringify(msg),
      headers: {
        Authorization: `Bearer ${env.SENDGRID_API_KEY}`,
        "Content-Type": "application/json",
      },
      method: "POST",
    });

      const personalizations = [{
          to: [{ email: to }],
        }];
      const msg = {
      personalizations,
      from: {
        email: fromAddress,
        name: fromName,
      },
      subject: subject,
      content: [{ type: "text/plain", value: plainText }],
    };
    const email = await fetch("https://api.sendgrid.com/v3/mail/send", {
      body: JSON.stringify(msg),
      headers: {
        Authorization: `Bearer ${env.SENDGRID_API_KEY}`,
        "Content-Type": "application/json",
      },
      method: "POST",
    });

      const personalizations = [{
          to: [{ email: to }],
        }];
      const msg = {
      personalizations,
      from: {
        email: fromAddress,
        name: fromName,
      },
      subject: subject,
      content: [{ type: "text/plain", value: plainText }],
    };
    const email = await fetch("https://api.sendgrid.com/v3/mail/send", {
      body: JSON.stringify(msg),
      headers: {
        Authorization: `Bearer ${env.SENDGRID_API_KEY}`,
        "Content-Type": "application/json",
      },
      method: "POST",
    });

Sorry if this looks clunky, it's picked straight out of my code. There's a bunch of things going on before the email gets sent.

Aalok ``` const personalizations = [{ to: [{ email: to }], }];...

N

Nick•3/25/24, 8:16 PM

looks like mine, but thanks, be useful to compare to

NNick looks like mine, but thanks, be useful to compare to 🙂

A

alok•3/25/24, 8:18 PM

Dump the response to console.log or whatever. Anything useful in there? Also, get it working with curl first might help you figure out what's going on.

N

Nick•3/25/24, 8:27 PM

oh thank god, it's working XD

N

Nick•3/25/24, 8:28 PM

well, locally that is

N

Nick•3/25/24, 8:28 PM

any recommendations for logging pages/workers when live? i feel so blind, even with the real-time logging. do i need to set up more?

Aalok I'm using Sendgrid by hitting Sendgrid's API directly with a fetch. It works but...

R

rob•3/25/24, 8:43 PM

yep i do the same, using the rest API via fetch

NNick any recommendations for logging pages/workers when live? i feel so blind, even w...

A

alok•3/25/24, 8:44 PM

I could be wrong, but with workers, you can setup logpush and log to r2 or a remote service. With pages, your only option is a tail worker? In any case, I would set something up, because the default logging is only a live view. You can't go back and query logs.

Aalok I could be wrong, but with workers, you can setup logpush and log to r2 or a rem...

N

Nick•3/25/24, 9:12 PM

tbh i'm not seeing any of my logs, even live

N

Nick•3/25/24, 9:12 PM

i see it when it crashes

C

codebam•3/25/24, 9:20 PM

../../node_modules/@cloudflare/ai/dist/ai/tasks/image-classification.d.ts(2,24): error TS2307: Cannot find module '../ai' or its corresponding type declarations.

../../node_modules/@cloudflare/ai/dist/ai/tasks/image-classification.d.ts(2,24): error TS2307: Cannot find module '../ai' or its corresponding type declarations.

../../node_modules/@cloudflare/ai/dist/ai/tasks/image-classification.d.ts(2,24): error TS2307: Cannot find module '../ai' or its corresponding type declarations.

../../node_modules/@cloudflare/ai/dist/ai/tasks/image-classification.d.ts(2,24): error TS2307: Cannot find module '../ai' or its corresponding type declarations.

the cloudflare ai package has broken imports

C

codebam•3/25/24, 9:22 PM

what's the last good version? if anyone knows

Ccodebam what's the last good version? if anyone knows

C

codebam•3/25/24, 9:38 PM

it's 1.0.53

1.1.0 has a problem with typescript imports

https://github.com/codebam/cf-workers-telegram-bot/pull/707

J

JCo•3/25/24, 9:41 PM

export const router = OpenAPIRouter({
    docs_url: "/",
    schema: {
        info: {
            title: "JCoNet LTD API",
            version: "1",
        },
        security: {
            ["apiKeyAuth"]: [],
        },
    },
});

router.registry.registerComponent("securitySchemes", "apiKeyAuth", {
    type: "apiKey",
    in: "header",
    name: "x-api-key",
});

console.log(router.schema);

export const router = OpenAPIRouter({
    docs_url: "/",
    schema: {
        info: {
            title: "JCoNet LTD API",
            version: "1",
        },
        security: {
            ["apiKeyAuth"]: [],
        },
    },
});

router.registry.registerComponent("securitySchemes", "apiKeyAuth", {
    type: "apiKey",
    in: "header",
    name: "x-api-key",
});

console.log(router.schema);

export const router = OpenAPIRouter({
    docs_url: "/",
    schema: {
        info: {
            title: "JCoNet LTD API",
            version: "1",
        },
        security: {
            ["apiKeyAuth"]: [],
        },
    },
});

router.registry.registerComponent("securitySchemes", "apiKeyAuth", {
    type: "apiKey",
    in: "header",
    name: "x-api-key",
});

console.log(router.schema);

export const router = OpenAPIRouter({
    docs_url: "/",
    schema: {
        info: {
            title: "JCoNet LTD API",
            version: "1",
        },
        security: {
            ["apiKeyAuth"]: [],
        },
    },
});

router.registry.registerComponent("securitySchemes", "apiKeyAuth", {
    type: "apiKey",
    in: "header",
    name: "x-api-key",
});

console.log(router.schema);

Anyone know why the security on this isnt working? Its the API example from the create command in my terminal, using the itty-router-openapi but I dont kow why security isnt being applied or shown.

K

Kevin•3/26/24, 1:23 AM

Have a fun one for the Workers team... itty-router is staged to release as v5, but we're running into an issue with the direct export signature.

Background:
An itty

Router

Router

Router

Router instance is a

Proxy

Proxy

Proxy

Proxy, with a

fetch

fetch

method. This matches the expected

{ fetch }

{ fetch }

{ fetch }

{ fetch } signature that Cloudflare or Bun expect. However, CF is having issues with the Proxy (Bun is fine with it, for comparison).

const router = Router()

// doesn't work (but should)
export default router

// works
export default {
  fetch: router.fetch
}

// works
export default { ...router }

const router = Router()

// doesn't work (but should)
export default router

// works
export default {
  fetch: router.fetch
}

// works
export default { ...router }

const router = Router()

// doesn't work (but should)
export default router

// works
export default {
  fetch: router.fetch
}

// works
export default { ...router }

const router = Router()

// doesn't work (but should)
export default router

// works
export default {
  fetch: router.fetch
}

// works
export default { ...router }

K

Kevin•3/26/24, 4:48 AM

PR Requests

I've identified an issue/bug with how the

{ middleware }

{ middleware }

{ middleware }

{ middleware } property of Workers exports is being treated. Is there a way for me to PR a fix to this directly?

K

kian•3/26/24, 5:39 AM

For Pages Functions?

K

kian•3/26/24, 5:39 AM

In any case, it's probably within Wrangler - there is no

middleware

middleware

middleware

middleware export as far as workerd is concerned

D

Denny•3/26/24, 11:09 AM

Do cancelled request also count towards Worker's request?
I have authentication via worker placed for video urls, every request is being served through worker before delivering the actual video content, Now here's the problem, if user scrubs through video timeline, browser invokes a lot of cancelled requests to video url. Are those requests be counted in worker requests?

VVikash Ohh, i am not sending from `vikash.rathee@gmail.com`, that's not my email id. Ju...

V

Vikash•3/26/24, 11:47 AM

Anyone from Cloudflare support?

S

Shakeskeyboarde•3/26/24, 2:18 PM

Is it possible to upload multiple worker files (vite dynamic import code splitting) using wrangler?

K

kian•3/26/24, 2:23 PM

So you can do

await import('foo.js')

await import('foo.js')

await import('foo.js')

await import('foo.js')? Yes

K

kian•3/26/24, 2:24 PM

Wrangler's default behaviour is to bundle everything (except WASM) into a single JS file, but you can tell it not to and it will upload all of the .JS files separately

i have to add type definitions or it manually or? did not mean to ping&*

Similar Threads

Similar Threads

Similar Threads