Thanks, that's fixed it! Really appreciate your help. Could I just clarify one more thing. Wrangler

MMitya Thanks, that's fixed it! Really appreciate your help. Could I just clarify one ...

H

Hard@Work•3/18/25, 5:24 PM

Wrangler shouldn't be running in production? Wrangler is used for development/deployment, but once deployed, Wrangler doesn't touch anything

M

MityaOP•3/18/25, 5:29 PM

Right, thanks, I think I thought Wrangler ran everywhere.

M

MityaOP•3/18/25, 5:30 PM

I assumed production used the same environment I had locally, in the same way that developing locally with PHP involves something like Apache, which is also on the live server.

MMitya I assumed production used the same environment I had locally, in the same way th...

H

Hard@Work•3/18/25, 6:17 PM

Sort of? Wrangler, under the hood, calls into Miniflare, which runs Workers in

workerd

workerd

workerd

workerd.

workerd

workerd

workerd

workerd does run in production, but the goal is for you to never need to care which version of

workerd

workerd

workerd

workerd is running

N

nikiv.dev•3/18/25, 10:05 PM

does workers with wrangler support

Buffer

Buffer

Buffer

Buffer?

J

James•3/18/25, 10:05 PM

yes

J

James•3/18/25, 10:05 PM

if you enable

nodejs_compat

nodejs_compat

nodejs_compat

nodejs_compat

N

nikiv.dev•3/18/25, 10:06 PM

N

nikiv.dev•3/18/25, 10:06 PM

how to get rid of this error, i installed types

N

nikiv.dev•3/18/25, 10:06 PM

https://github.com/nikitavoloboev/api-ts-hono

N

nikiv.dev•3/18/25, 10:07 PM

oh ok

N

nikiv.dev•3/18/25, 10:07 PM

i think its this

N

nikiv.dev•3/18/25, 10:10 PM

https://developers.cloudflare.com/changelog/2025-03-17-importable-env/ im confused

N

nikiv.dev•3/18/25, 10:10 PM

i can do this, but where to put the env

I

iano•3/19/25, 4:14 PM

Wrangler rewrites the request URL being sent to localhost into the custom domain which is set in wrangler.jsonc. Is that expected? It is very surprising to me?

I

iano•3/19/25, 4:15 PM

(So for example if I curl http://localhost:8787/ with a console.log in the fetch the fetch sees a request to url custom-domain.com even though its running locally)

J

jonasb•3/19/25, 8:19 PM

Hey

Now when wrangler@4 generates all the types, does anyone have guidance as to how to build libraries that depend on e.g. D1Database? For https://github.com/jonasb/d1-sql-tag I'm using

@cloudflare/workers-types

@cloudflare/workers-types

@cloudflare/workers-types

@cloudflare/workers-types , but get incompabilities when e.g. upgrading wrangler

GitHub

GitHub - jonasb/d1-sql-tag: A template literal for working with Clo...

A template literal for working with Cloudflare D1 database. - jonasb/d1-sql-tag

M

MSP2.Leaks•3/20/25, 12:26 PM

Who pinged me

Ppenalosa If you're using `@cloudflare/workers-types`, make sure you're using the `/experi...

E

echoes221•3/20/25, 3:00 PM

I've noticed that the types generated by wrangler 4.2.0 break on import when using Env as it extends cloudflare.env in the namespace, on 4.0.0 this is fine with no extension. Was this an accidental breaking change? When I say break, I mean that the values don't resolve to the namespace correctly after typegen.

Ppenalosa Could you give an example of how it's broken for you?

E

echoes221•3/20/25, 5:03 PM

Sure, here is 4.0.0 in the first image, I generally read from Env type where I need it. In 4.2.0 its this

interface Env extends Cloudflare.Env {}

interface Env extends Cloudflare.Env {}

interface Env extends Cloudflare.Env {}

interface Env extends Cloudflare.Env {}. On further inspection, its when there's a durable object namespace in the types, it doesn't resolve (I'd removed the types to keep it short for this example and it worked). But it's completely fine if the type isn't extended

Ppenalosa We've changed how that file is generated, but it shouldn't cause any breakage in...

E

echoes221•3/20/25, 5:21 PM

It's the fact that types are no longer found in the rest of the codebase if extending from Cloudflare.Env AND if there is a durable object in there that imports (e.g.

    ORGANISATION_PERFORMANCE_REPORT: DurableObjectNamespace<import("./workers/app").organisationPerformanceReportDO>;

ORGANISATION_PERFORMANCE_REPORT: DurableObjectNamespace<import("./workers/app").organisationPerformanceReportDO>;

    ORGANISATION_PERFORMANCE_REPORT: DurableObjectNamespace<import("./workers/app").organisationPerformanceReportDO>;

ORGANISATION_PERFORMANCE_REPORT: DurableObjectNamespace<import("./workers/app").organisationPerformanceReportDO>;).
You're unable to jump to the typedef, and typescript/IDE throws up errors as they cannot be resolved. Its not possible to cmd + click into the type any longer. I'm using Typescript v5.7.3

Ppenalosa We've changed how that file is generated, but it shouldn't cause any breakage in...

E

echoes221•3/20/25, 5:26 PM

Easier with a vid to show

Ddan I can't seem to get the new process.env flag to work...I have this in my wrangle...

T

telliks•3/21/25, 12:30 PM

Did you manage to figure this one out? I'm also having a difficult time getting this to work (locally and deployed)

T

telliks•3/21/25, 12:34 PM

My expectation might be wrong here. If I set the

nodejs_compat_populate_process_env

nodejs_compat_populate_process_env

nodejs_compat_populate_process_env

nodejs_compat_populate_process_env compatibility flag with a compatibility date of "2025-03-17", should the env vars defined in my

.dev.vars

.dev.vars

.dev.vars

.dev.vars be populated in

process.env

process.env

process.env

process.env when running locally?

Ttelliks My expectation might be wrong here. If I set the `nodejs_compat_populate_process...

T

telliks•3/21/25, 2:01 PM

Created a brand new most basic worker and it works as expected. It must be some other incompatibility in my react-router-7 + vite setup then.

Ttelliks Created a brand new most basic worker and it works as expected. It must be some ...

D

dan•3/21/25, 2:37 PM

I think it's an issue with the vite plugin, I was trying to do it in the agents starter, but when i go to a normal wrangler setup (with 02-28 compat date) it works fine

Ddan I think it's an issue with the vite plugin, I was trying to do it in the agents ...

T

telliks•3/21/25, 2:54 PM

I wonder if vite is not clearing the

process.env

process.env

process.env

process.env when running client side. What I noticed now is that I can access

process.env

process.env

process.env

process.env vars in react-router loaders that run server-side, but those vars are not defined on

process.env

process.env

process.env

process.env for client-side code, even when prepended with

VITE_PUBLIC_

VITE_PUBLIC_

VITE_PUBLIC_

VITE_PUBLIC_.

D

dan•3/21/25, 3:07 PM

yeah it's probably overwriting it

E

echoes221•3/21/25, 8:17 PM

I've been attempting to get

@cloudflare/vite-plugin

@cloudflare/vite-plugin

@cloudflare/vite-plugin

@cloudflare/vite-plugin working and running up against a bit of a wall when starting the app (with RRv7). I'm getting a

"AssertionError: depsOptimizer is required in dev mode"

"AssertionError: depsOptimizer is required in dev mode"

"AssertionError: depsOptimizer is required in dev mode"

"AssertionError: depsOptimizer is required in dev mode" |

[plugin:vite:import-analysis] depsOptimizer is required in dev mode

[plugin:vite:import-analysis] depsOptimizer is required in dev mode

[plugin:vite:import-analysis] depsOptimizer is required in dev mode

[plugin:vite:import-analysis] depsOptimizer is required in dev mode error, which appears to come up when the source is a node module? I extended the the assertion for the source that's failing and it looks like its

AssertionError: depsOptimizer is required in dev mode for node:crypto

AssertionError: depsOptimizer is required in dev mode for node:crypto

AssertionError: depsOptimizer is required in dev mode for node:crypto

AssertionError: depsOptimizer is required in dev mode for node:crypto.

Is there any compatibility issue with node modules with the vite plugin?

P

Paul•3/24/25, 5:39 AM

I'm considering using Cloudflare Pages + Durable Objects with SQL on a new project, with Sveltekit as the framework, and came across the issues described here:

https://github.com/sveltejs/kit/issues/1712

Long story short, the durable object can't be in the same wrangler project as the sveltekit project (at least according to the most recent comment in this issue)

Is this still the case? The workaround looks pretty iffy - a monorepo with 2 wrangler projects, one for the DO and one for Sveltekit, then named bindings linking the 2 and some bodges to proxy requests between the projects when testing locally.

I note there's a Beta feature "Frameworks" - does this have the same issue with not allowing DO's to be hosted in the same wrangler project?

A

awful•3/25/25, 12:54 AM

I was in the process of updating pages to 0.0.16 when I got an error: Cannot find module '/Users/username/.npm/_npx/769b1efcb4c28da2/node_modules/pages/node_modules/coffee-script'

I have tried to do npm install -g coffee-script as well as npm install -g coffeescript. I have also tried to uninstall wrangler.

I am on an Intel MacBook Pro and using Sonoma 14.6.1.

J

James•3/25/25, 2:09 AM

What is the

pages

pages

pages

pages npm package and why would you need it? That’s over a decade old and for AngularJS and almost certainly won’t work in Workers

JJames What is the `pages` npm package and why would you need it? That’s over a decade ...

A

awful•3/25/25, 2:38 AM

https://developers.cloudflare.com/workers/wrangler/commands/#pages

J

James•3/25/25, 2:38 AM

That’s a wrangler command - you don’t need to install

pages

pages

pages

pages from npm.

npx wrangler pages dev

npx wrangler pages dev

npx wrangler pages dev

npx wrangler pages dev for example will run a local dev server for Cloudflare Pages

A

awful•3/25/25, 2:39 AM

Thanks I probably forgot to type wrangler

A

adt•3/25/25, 12:51 PM

Hey All! Im trying to run an Astro SSR app with cloudflare. I'm having type conflicts with the wrangler generated types when calling client side web apis from a client side script... For example, calling fetch from a client side script will reference the workerd fetch type and not the web api. Is there a work around or am i missing something?

C

Cibulka•3/26/25, 5:36 PM

Why don't my static files load

C

Cibulka•3/26/25, 5:36 PM

all of them just give 404 errors

V

veeque•3/26/25, 5:59 PM

running

wrangler d1 execute --help

wrangler d1 execute --help

wrangler d1 execute --help

wrangler d1 execute --help I see the option for

-y

-y

-y

-y. Is there the opposite?

-n

-n

-n

-n? I need to have the

.sql

.sql

.sql

.sql file for D1 be created (to get its name) by running

wrangler d1 execute id-development -e development --command ' ' --local

wrangler d1 execute id-development -e development --command ' ' --local

wrangler d1 execute id-development -e development --command ' ' --local

wrangler d1 execute id-development -e development --command ' ' --local which will result in an error and I don't think spamming Cloudflare with random stuff is something I should do

V

veeque•3/26/25, 6:10 PM

When the command fails it asks:

Would you like to report this error to Cloudflare? Wrangler's output and the error details will be shared with the Wrangler team to help us diagnose and fix the issue. (Y/n)

Would you like to report this error to Cloudflare? Wrangler's output and the error details will be shared with the Wrangler team to help us diagnose and fix the issue. (Y/n)

Would you like to report this error to Cloudflare? Wrangler's output and the error details will be shared with the Wrangler team to help us diagnose and fix the issue. (Y/n)

Would you like to report this error to Cloudflare? Wrangler's output and the error details will be shared with the Wrangler team to help us diagnose and fix the issue. (Y/n)

, and using

-y

-y

-y

-y would say yes every time, also

| yes n

| yes n

| yes n

| yes n is not an option

V

veeque•3/26/25, 6:49 PM

ohh that one's good, ty

D

dan•3/26/25, 8:04 PM

does anyone have any tips for working with

wrangler types

wrangler types

wrangler types

wrangler types in monorepo packages? I have multiple workers that can bind to one another (as well as DOs) but I'm not sure how to get a typed reference to

workers/my-agent

workers/my-agent

workers/my-agent

workers/my-agent from

apps/api

apps/api

apps/api

apps/api without

apps/api

apps/api

apps/api

apps/api importing from

workers

workers

workers

workers (which I don't want)

D

dan•3/26/25, 8:05 PM

this is really annoying and common in my codebase right now, i'm in a monorepo package that shouldn't depend on a worker in the monorepo so i have no idea how to resolve these types

Thanks, that's fixed it! Really appreciate your help. Could I just clarify one more thing. Wrangler

Similar Threads

Similar Threads

Similar Threads