tsx chokes on this import `import { DurableObject } from "cloudflare:workers";` `Error [ERR_UNSUPPOR

tsx chokes on this import

import { DurableObject } from "cloudflare:workers";

import { DurableObject } from "cloudflare:workers";

Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. Received protocol 'cloudflare:'

Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. Received protocol 'cloudflare:'

Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. Received protocol 'cloudflare:'

Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. Received protocol 'cloudflare:'

sl0wik•11/12/24, 3:58 PM

My image-transforming worker just stopped working. Returnig response ignoring cf: image: {width: 300, height: 300, fit: 'cover', draw: null}.

Is anyone familiar with changes? I had it before with billing issues but all looks normal.

Ssl0wik My image-transforming worker just stopped working. Returnig response ignoring cf...

fry69•11/12/24, 4:00 PM

Open a ticket?

fry69•11/12/24, 4:00 PM

?support

Flare•11/12/24, 4:00 PM

To contact Cloudflare Support about an issue, please visit the Support Portal and fill in the form on the portal. After submission, you will receive confirmation over email.

Some issues, such as Account or Billing related issues, cannot be solved by the community.
Any plan level (including Free plans) can open tickets for Account, Billing or Registrar ticket categories. Make sure to select the correct category to ensure it goes to the right place.
For more information on the methods by which you can contact Support for your plan level, see Contacting Cloudflare Support - Cloudflare Docs

Ffry69 Open a ticket?

sl0wik•11/12/24, 4:16 PM

Are you aware is support ticket login would be the same as account login?

Jjohtso tsx chokes on this import `import { DurableObject } from "cloudflare:workers";` ...

.gwapes•11/12/24, 5:34 PM

Does

@cloudflare/workers

@cloudflare/workers

work?

Constantin•11/12/24, 6:01 PM

hey there, do you have any snappy suggestion for generating pdfs with a worker?

Constantin•11/12/24, 6:02 PM

oh, found the lazyinvoice one

森

森@VerseLink (RW)•11/12/24, 8:02 PM

I think I might have found a bug with miniflare, can someone also confirm this is also a issue?

Reproduction step:
Passing a ReadableStream through a service binding RPC call

森

森@VerseLink (RW)•11/12/24, 8:02 PM

this is what it throws

森

森@VerseLink (RW)•11/12/24, 8:21 PM

and if you attempt to pass a Request with a body as a RPC call, you will get:

森

森@VerseLink (RW)•11/12/24, 8:21 PM

i feel like RPC with miniflare is exteremely buggy and I hope I'm not the one feeling about this

森森@VerseLink (RW)I think I might have found a bug with miniflare, can someone also confirm this i...

森

森@VerseLink (RW)•11/12/24, 8:26 PM

i think i figured out what might be happening, i'm trying to upload a file via rpc binding by passing readable stream; while the document says it supports passing readable stream / writable stream, the source code of miniflare seems to only support the case where we pass in readable stream and the rpc code expects a writable stream (or the other way around) to be returned by the code

森

森@VerseLink (RW)•11/12/24, 8:26 PM

i'm not sure if this is a bug, or a documentation error

森

森@VerseLink (RW)•11/12/24, 8:26 PM

can anyone confirm this?

森

森@VerseLink (RW)•11/12/24, 8:27 PM

(i'm leaning towards as a bug as it's an assertion error and not a explicit error being thrown)

森森@VerseLink (RW)(i'm leaning towards as a bug as it's an assertion error and not a explicit erro...

DaniFoldi•11/12/24, 8:29 PM

I recommend checking if there's a github issue for this, and if not, opening one - I also don't see a reason why it shouldn't work, and even if that is the case, the team can confirm

森

森@VerseLink (RW)•11/12/24, 8:33 PM

closest thing i could find is:
https://github.com/cloudflare/workers-sdk/issues/6047
which is never really fixed (this really hurts the dev experience btw)
but this is related to the second issue with RPC calls and not the first

GitHub

🐛 BUG: Miniflare R2 writeHttpMetadata - DevalueError: Cannot string...

Which Cloudflare product(s) does this pertain to? R2, Miniflare What version(s) of the tool(s) are you using? 3.60.3 [wrangler], 3.20240610.0 [miniflare] What version of Node are you using? 18.18.2...

LordSilver•11/12/24, 9:00 PM

How do you call the bolt thing kind of communication?

LordSilver•11/12/24, 9:01 PM

That's not true RPC right? Because RPC would generally involve a network boundary. A request going from microservice X to microservice Y through a service mesh. But in this case the two services are colocated in the same workspace so there's no actual network request.

森

森@VerseLink (RW)•11/12/24, 9:01 PM

just service binding, you can also invoke it the HTTP way (and not RPC)

森

森@VerseLink (RW)•11/12/24, 9:03 PM

the rest i guess is implementation details, i don't think there's a guarantee that the two services would be in the same workspace or even server at all; and in reality, most cross application boundary communications uses some form of RPC anyways, where they are on the same machine or not

daniel•11/12/24, 9:09 PM

my worker sends requests to a specific server on the cloudflare network. it's been working for months and it was working this morning but i just started receiving this error out of nowhere (no deployed code changes in the last few weeks on my worker).

can an employee confirm whether a change was made recently to block access to certain cloudflare ips from workers?

森森@VerseLink (RW)just service binding, you can also invoke it the HTTP way (and not RPC)

LordSilver•11/12/24, 9:36 PM

but that's just a fake HTTP, it's still using same magic under the hood

Isaac McFadyen•11/12/24, 9:48 PM

^ RPC is invariant of transport

Isaac McFadyen•11/12/24, 9:48 PM

You can RPC over a unix socket, over IPC boundaries, or over a network connection

Isaac McFadyen•11/12/24, 9:48 PM

Or even RPC in shared memory as is the case with some apps (see Tauri for example)

森

森@VerseLink (RW)•11/12/24, 10:36 PM

... sorry can i vent for a bit?

森

森@VerseLink (RW)•11/12/24, 10:36 PM

or if someone could let me know is there a better solution

森

森@VerseLink (RW)•11/12/24, 10:36 PM

how exactly do you detect if the worker is in dev mode or in production mode?

森

森@VerseLink (RW)•11/12/24, 10:37 PM

it looks like the official solution is to add [env.dev] and add something like ENVIRONMENT = "dev"

森

森@VerseLink (RW)•11/12/24, 10:37 PM

if that's the case....

森

森@VerseLink (RW)•11/12/24, 10:37 PM

then why is the majority of keys "NOT INHERITABLE"

森

森@VerseLink (RW)•11/12/24, 10:38 PM

why?
if it works both in staging / prod and dev, why should i have to copy every single vars under env.dev ?

森

森@VerseLink (RW)•11/12/24, 10:39 PM

i have like an array of vars that define a certain default output

森

森@VerseLink (RW)•11/12/24, 10:39 PM

does that mean i have to copy the whole thing under [env.dev]?

森

森@VerseLink (RW)•11/12/24, 10:40 PM

ok, if that's the case, and I decided that I would change the non-dev vars just because i want a different set of output, does that mean i need to remember to also change env.dev too? I already can see myself debugging only to realize i forgot to change the [env.dev] too because the non dev vars were changed...

森

森@VerseLink (RW)•11/12/24, 10:54 PM

....omg

森

森@VerseLink (RW)•11/12/24, 10:55 PM

now running wrangler dev --env devwrangler dev --env dev causes service binding to freak out and screams Cannot access '{functionName}' as we couldn't find a 'wrangler dev' session for service "{service}" to proxy to.Cannot access '{functionName}' as we couldn't find a 'wrangler dev' session for service "{service}" to proxy to.

森

森@VerseLink (RW)•11/12/24, 11:07 PM

I found the solution

森

森@VerseLink (RW)•11/12/24, 11:11 PM

kind of hacky, not intended; not sure if the wrangler dev session thing is a bug or not, don't care to reproduce it on a more basic setup.
but if brave traveler if you stumble upon this message; instead of using [env], use

.dev.vars

.dev.vars

! yes, it's not meant for local dev and more for secrets; but percisely, you can use this to your advandage that the value of

.dev.vars

.dev.vars

is local to your machine!
(note: this would also cause 'but this works on my machine problem', best to document this and note that include

.dev.vars

.dev.vars

and with an environment variable to indicate it's in development)

森

森@VerseLink (RW)•11/12/24, 11:12 PM

not sure why that cf-workers has "node:process" included, but never process.env.NODE_ENV === 'development'process.env.NODE_ENV === 'development' which should be a simple implementation

森森@VerseLink (RW)not sure why that cf-workers has "node:process" included, but never `process.env...

Isaac McFadyen•11/12/24, 11:53 PM

Because only recently node:processnode:process was introduced into the runtime (recent = months/years). If they had added this at the same time, then existing code that checks for NODE_ENVNODE_ENV to determine whether it's running in Workers or Node would break

IIsaac McFadyen Because only recently `node:process` was introduced into the runtime (recent = m...

森

森@VerseLink (RW)•11/12/24, 11:58 PM

oh yeh, great argument!

Well, I still think people would benefit a lot if it's simple to detect what env they are in via something similar, perhaps process.env.WORKER_ENVprocess.env.WORKER_ENV or a standalone global variable since env is per fetch and not global, so it be also nice to check this can be checked globally sometimes, I guess?

Since a lot of frameworks does things similar to this (for example app.Environment.IsDevelopment()app.Environment.IsDevelopment() in ASP like webservers), I was sort of bummed out that the official way to detect development/staging/prod is via [env], which comes with a whole baggage of concerns like non inherit keys; and also aformentioned bug about not find the session (I'll write up a bug report for it :/)

Ddaniel my worker sends requests to a specific server on the cloudflare network. it's be...

Nicolas•11/13/24, 9:34 AM

Got the same issue

RRam Is anyone using Browser rendering at scale? I'm wondering what the pricing looks...

Advany•11/13/24, 11:59 AM

I am, its working pretty good. The durable object isn't that big of a cost factor if you use it at scale. Maximum like $10 dollars a month orso? That you use it like 24/7. As currently there are not session costs?

tadhglewis•11/13/24, 1:01 PM

Is there known ongoing issues with Workers Builds? Two of my Workers have been timing out at cloing repo step for the past >3 days

2024-11-10T16:59:08.974Z    Initializing build environment...
2024-11-10T16:59:18.008Z    Success: Finished initializing build environment
2024-11-10T16:59:18.360Z    Cloning repository...
2024-11-10T17:19:08.252Z    Build was timed out

2024-11-10T16:59:08.974Z    Initializing build environment...
2024-11-10T16:59:18.008Z    Success: Finished initializing build environment
2024-11-10T16:59:18.360Z    Cloning repository...
2024-11-10T17:19:08.252Z    Build was timed out

I was in the Builds cache beta and I'm using watch paths so not sure if that's related

tadhglewis•11/13/24, 1:17 PM

I've tried reconnecting GitHub integration and still same issue

tsx chokes on this import `import { DurableObject } from "cloudflare:workers";` `Error [ERR_UNSUPPOR

Similar Threads

Similar Threads

Similar Threads