Just got to wait. AFAIK, it isn't even in private beta yet, so it might be a little while before it

A

Advany•2/28/23, 8:19 PM

Got it! Will use browserless in the mean time in my workers

HHello, I’m Allie!Just got to wait. AFAIK, it isn't even in private beta yet, so it might be a lit...

D

dave•2/28/23, 8:25 PM

what's the feature list supposed to be? I have something similar to this on my TODO list I think

Ddave what's the feature list supposed to be? I have something similar to this on my T...

H

Hello, I’m Allie!OP•2/28/23, 8:26 PM

https://blog.cloudflare.com/introducing-workers-browser-rendering-api/

The Cloudflare Blog

Automate an isolated browser instance with just a few lines of code

Workers Browser Rendering API is our out-of-the-box solution for simplifying developer workflows, including capturing images or screenshots, by running browser automation in Workers. If you’re interested, sign up for the waitlist.

Mm0c what is the currently recommended approach for testing? I see 2 different approa...

H

Hello, I’m Allie!OP•2/28/23, 9:52 PM

Vitest would probably be best, as it supports hooking into the Vitest family of testing utilities, while

unstable_dev

unstable_dev

unstable_dev

unstable_dev just allows you to run

wrangler dev

wrangler dev

without the CLI.

J

johtso•2/28/23, 11:16 PM

do static "bucket" assets count towards the worker size limits?

J

johtso•2/28/23, 11:20 PM

I'm guessing not..

Original message was deleted

J

johtso•2/28/23, 11:32 PM

yep

D

dave•2/28/23, 11:51 PM

How do I avoid this issue?

[NPXI] @miniflare/tre not available locally. Attempting to use npx to install temporarily.
[NPXI] Installing... (npx --prefer-offline -y -p @miniflare/tre@3.0.0-next.12)

[NPXI] @miniflare/tre not available locally. Attempting to use npx to install temporarily.
[NPXI] Installing... (npx --prefer-offline -y -p @miniflare/tre@3.0.0-next.12)

[NPXI] @miniflare/tre not available locally. Attempting to use npx to install temporarily.
[NPXI] Installing... (npx --prefer-offline -y -p @miniflare/tre@3.0.0-next.12)

[NPXI] @miniflare/tre not available locally. Attempting to use npx to install temporarily.
[NPXI] Installing... (npx --prefer-offline -y -p @miniflare/tre@3.0.0-next.12)

D

dave•2/28/23, 11:53 PM

yarn add -D @miniflare/tre@3.0.0-next.12

yarn add -D @miniflare/tre@3.0.0-next.12

yarn add -D @miniflare/tre@3.0.0-next.12

yarn add -D @miniflare/tre@3.0.0-next.12

Like this?

Original message was deleted

D

dave•2/28/23, 11:53 PM

yeah, I thought it would be a better idea to use this instead of miniflare?

K

kian•3/1/23, 12:28 AM

In a Service Binding or just a normal inbound request?

K

kian•3/1/23, 12:30 AM

In the Quick Edit preview of the dashboard or actually deployed?

K

kian•3/1/23, 12:32 AM

Yeah

K

kian•3/1/23, 12:32 AM

It won't exist in preview since the preview isn't quite a 'real' Worker

K

kian•3/1/23, 12:32 AM

I'd always recommend publishing it or using

wrangler dev

wrangler dev

locally for a proper preview environment

D

dave•3/1/23, 1:22 AM

Is there something like this, but for Cloudflare Workers? https://stoplight.io/open-source/prism

K

kian•3/1/23, 10:04 AM

Just an Authorization header

K

kian•3/1/23, 10:04 AM

export default {
  fetch(req) {
    const username = "user";
    const password = "passwd";
    const b64 = btoa(`${username}:${password}`);

    return fetch("https://httpbin.org/basic-auth/user/passwd", {
      headers: {
        Authorization: `Basic ${b64}`,
      },
    });
  },
};

export default {
  fetch(req) {
    const username = "user";
    const password = "passwd";
    const b64 = btoa(`${username}:${password}`);

    return fetch("https://httpbin.org/basic-auth/user/passwd", {
      headers: {
        Authorization: `Basic ${b64}`,
      },
    });
  },
};

export default {
  fetch(req) {
    const username = "user";
    const password = "passwd";
    const b64 = btoa(`${username}:${password}`);

    return fetch("https://httpbin.org/basic-auth/user/passwd", {
      headers: {
        Authorization: `Basic ${b64}`,
      },
    });
  },
};

export default {
  fetch(req) {
    const username = "user";
    const password = "passwd";
    const b64 = btoa(`${username}:${password}`);

    return fetch("https://httpbin.org/basic-auth/user/passwd", {
      headers: {
        Authorization: `Basic ${b64}`,
      },
    });
  },
};

K

Kai•3/1/23, 11:47 AM

I remember that I read that workers where charged for the duration that it proxied a websocket on the unbound plan. has it changed or does that still stand?

Z

zegevlier•3/1/23, 12:57 PM

That seems to need headless chrome. You can't run that on workers. However, there is something called the rendering API that might also offer this when it comes out.

Z

zegevlier•3/1/23, 12:58 PM

https://blog.cloudflare.com/introducing-workers-browser-rendering-api/

The Cloudflare Blog

Automate an isolated browser instance with just a few lines of code

Workers Browser Rendering API is our out-of-the-box solution for simplifying developer workflows, including capturing images or screenshots, by running browser automation in Workers. If you’re interested, sign up for the waitlist.

G

GuillaumeLakano•3/1/23, 3:46 PM

Hi! We are on a paid plan for workers since 2020, and I'm trying for the 1st time to change in my wrangler.toml the usage_model to "unbound", but I got this error:
« workers.api.error.wrong_plan [code: 10075] »

Do I have to enable something to uses it ?

Nnittolinho Hi everyone! I was wondering if it would be possible to insert lighthouse-ci on ...

C

cdslash•3/1/23, 3:58 PM

I've been trying to do the same thing - have applied for the rendering waitlist so hopefully it doesn't take too long to get into the beta.

GGuillaumeLakano Hi! We are on a paid plan for workers since 2020, and I'm trying for the 1st tim...

G

GuillaumeLakano•3/1/23, 4:04 PM

Just found a workaround, in Workers « Default Usage Model », even if you don't want "unbound" as the default usage models, change it one time on unbound, this activate it on your account, then you can re-turn again on « Default Usage Model » to change it back to « bundled » if it's your preference like us.

GGuillaumeLakano Hi! We are on a paid plan for workers since 2020, and I'm trying for the 1st tim...

E

Erisa•3/1/23, 6:05 PM

Most likely you're trying to use Unbound and have a legacy plan that doesn't support unbound.
If you're an Enterprise customer you'll have to contact your account team, if not then there should be a prompt somewhere on the dashboard to enable Unbound

GGuillaumeLakano Just found a workaround, in Workers « Default Usage Model », even if you don't w...

E

Erisa•3/1/23, 6:06 PM

Oh seeing this now, yeah, that sounds like it would work

P

Piero•3/1/23, 8:28 PM

Just discovered that workers can be run as cron jobs and wow this is such an amazing feature!

C

Cyb3r-Jak3•3/1/23, 10:22 PM

Has anyone ever come accross the error

Trace: TypeError: Found invalid object in transferList

Trace: TypeError: Found invalid object in transferList

Trace: TypeError: Found invalid object in transferList

Trace: TypeError: Found invalid object in transferList when caching a response? The code I have is

if (response.status !== 404) {
        response.headers.set("cache-control", "max-age=3600")
        c.executionCtx.waitUntil(cache.put(req, response.clone()))
    }

if (response.status !== 404) {
        response.headers.set("cache-control", "max-age=3600")
        c.executionCtx.waitUntil(cache.put(req, response.clone()))
    }

if (response.status !== 404) {
        response.headers.set("cache-control", "max-age=3600")
        c.executionCtx.waitUntil(cache.put(req, response.clone()))
    }

if (response.status !== 404) {
        response.headers.set("cache-control", "max-age=3600")
        c.executionCtx.waitUntil(cache.put(req, response.clone()))
    }

and if I comment it out then I don't get the error. It only happens on this one endpoint

C

Cyb3r-Jak3•3/1/23, 10:35 PM

Found it: https://github.com/cloudflare/miniflare/issues/527

CCyb3r-Jak3 Found it: https://github.com/cloudflare/miniflare/issues/527

J

James•3/1/23, 10:43 PM

Oh good, I've been seeing this all over my dev today and assumed it was related to an update of something. Didn't have chance to dig-in yet though

JJames Oh good, I've been seeing this all over my dev today and assumed it was related ...

D

dave•3/1/23, 11:42 PM

my gut tells me this is a mitigation for a dangling arraybuffer issue lol