in `@cloudflare/vite-plugin`'s readme i see a section titled "migrating from `wrangler dev`". now, d

@cloudflare/vite-plugin

@cloudflare/vite-plugin

's readme i see a section titled "migrating from

wrangler dev

wrangler dev

". now, does that mean that, going forward, one should aim to use this?

i often get very confused by what's the direction going forward (is pages gonna get deprecated in favour of worker assets? no idea). same here. it would be nice if in the docs, or somewhere, there was even just a simple list that lists the things that will be used going forward, and what will be deprecated some time in the futer (aka: if you want, you can already start moving away from it if the replacement's downsides don't affect you)

Vveeque in `@cloudflare/vite-plugin`'s readme i see a section titled "migrating from `wr...

Silvan•3/3/25, 6:53 PM

I had the same question before. they wont call pages deprecated yet but now that worker assets supports even more things that were “special” for pages its fairly clear to me that its the way going forward. pages just dosent integrate as nicely

veequeOP•3/3/25, 6:54 PM

i've had the same feeling, but not having a clear way to know all this aside from working at cf is kinda annoying :‘)

TTilo Will there be support for local browser rendering development? And or Queues in ...

Kathy•3/3/25, 7:02 PM

re: browser rendering.
not yet, but on roadmap

BumblebeeSquare•3/3/25, 7:10 PM

how do i do local dev with pages + DO RPC in sveltekit ? previously i was using this PR https://github.com/cloudflare/workers-sdk/pull/7098 but the package is expired and getPlatformProxy does not support added wrangler arguments as this PR mentioned https://github.com/cloudflare/workers-sdk/issues/7842

GitHub

Support multi-worker Durable Object RPC by RamIdeas · Pull Request ...

Fixes #5918
Support Durable Object RPC across multiple wrangler instances
Only supports RPC method calls right now. RPC property access is coming shortly (in this PR)
The entire implementation is i...

GitHub

🚀 Feature Request: Support multiple config files in getPlatformProx...

Describe the solution Regarding this pull request fixing this issue, allowing running multiple worker projects with a pages project, can we support multiple config files in getPlatformProxy? Someth...

EEdmund Hung Hi everyone! It's the Wrangler office hours—feel free to post any questions you ...

Shufflepuff•3/3/25, 7:15 PM

When will we be able to set pages secrets via wrangler github action

I'd love to have this https://github.com/cloudflare/wrangler-action/issues/304

GitHub

uploading environment secrets doesn't work with pages deploy · Issu...

wrangler-action/src/index.ts Line 251 in cd8a317 const args = ["wrangler", "secret:bulk"]; When the repository is pages directory, it needs to run wrangler pages secret bulk Oth...

Vveeque in `@cloudflare/vite-plugin`'s readme i see a section titled "migrating from `wr...

BumblebeeSquare•3/3/25, 7:20 PM

im also intersted on migrating from pages to workers, i really need that observability and all the missing features...

is there an plan to help ppl migrate to workers+static asset for frameworks i.e sveltekit, how will custom domain update pagess -> worker
i wonder how service binding work with frameworks i.e sveltekit, can a worker bind to sveltekit "rpc" "route" or i need to use fetch in dev

1.1.1.1APP•3/3/25, 9:48 PM

DNS over Discord: GitHub

View the DNS over Discord source code on GitHub at https://dns-over-discord.v4.wtf/github

EEdmund Hung It supports Workers + static assets only at the moment.

Victor•3/3/25, 10:03 PM

Are there plans to bring this to pages eventually? Or only workers + static assets with pages being discontinued?

VVictor Are there plans to bring this to pages eventually? Or only workers + static asse...

JacobMGEvans•3/5/25, 12:08 AM

I dont know the official answer, my guess is just Workers + Static, since Pages is being phased out. It would be some work for something that would be phased out

banny`•3/5/25, 5:26 AM

I accidentally ran a migration for a durable object. Is it possible i can delete those migration tags from my worker?

Mitya•3/6/25, 4:43 PM

Wrangler hangs when shutting down a local worker using

--remote

--remote

have put the details Wrangler hangs on "Shutting down remote preview..."

Murder Chicken•3/6/25, 4:46 PM

When using

npx wrangler dev --test-scheduled -c path/wranglerA/wrangler.toml -c path/wranglerB/wrangler.toml

npx wrangler dev --test-scheduled -c path/wranglerA/wrangler.toml -c path/wranglerB/wrangler.toml

to run multiple workers at the same time with a single command, is it possible to have the

scheduled

scheduled

handler executed on all workers? As it operates now, it seems as though using

/__scheduled

/__scheduled

is only executed on the primary worker (i.e., the first one in the command chain).

onnimonni•3/6/25, 6:00 PM

Is there a way to create separate access tokens from cli?

I would want to store my opentofu state in R2 bucket and I can easily create the bucket with wrangler

wrangler r2 bucket create my-terraform-state

wrangler r2 bucket create my-terraform-state

but I can't create the access tokens in a similiar manner.

Oonnimonni Is there a way to create separate access tokens from cli? I would want to store...

Hard@Work•3/6/25, 6:10 PM

Wrangler does not currently support token operations. You would need to use this API: https://developers.cloudflare.com/api/resources/accounts/subresources/tokens/methods/create/

Cloudflare API | Accounts › Tokens › Create Token

Interact with Cloudflare's products and services via the Cloudflare API

Rafa•3/6/25, 6:40 PM

preview

SShufflepuff When will we be able to set pages secrets via wrangler github action 😊 I'd love...

flashblaze•3/7/25, 2:45 PM

I wrote a "hacky" blog post which might help you: https://flashblaze.xyz/posts/environment-variables-in-cloudflare-pages

MMitya Wrangler hangs when shutting down a local worker using `--remote` - have put the...

Mitya•3/7/25, 3:31 PM

Anyone from CF able to comment/help here?

MMitya Anyone from CF able to comment/help here?

Cyb3r-Jak3•3/7/25, 4:47 PM

Your best bet for official support is to open an issue on the workers-SDK repo

ZachHandley•3/7/25, 5:52 PM

Hey why doesn't cloudflare pages redirect www well

ZZachHandley Hey why doesn't cloudflare pages redirect www well

Hard@Work•3/7/25, 5:57 PM

This is the #wrangler channel, you probably want #workers-and-pages-discussions

ZachHandley•3/7/25, 5:57 PM

okey ty

klouzo35•3/8/25, 6:08 AM

Hi, for my project I'm using Nuxt 3 with deployement on Cloudflare Pages. Why in my build logs the Wrangler version is 3.101.0 :

15:57:46.479 Checking for configuration in a Wrangler configuration file (BETA)
15:57:46.480
15:57:47.580 No wrangler.toml file found. Continuing.
15:57:47.581 Found _worker.js in output directory. Uploading.
15:57:47.587

wrangler 3.101.0

But in my package.json it is "wrangler": "^3.111.0" ?

JJacob Marshall I recently ran into a similar issue (sharing resources between workers) and I be...

alex (he/him)•3/8/25, 6:37 AM

Sorry to ping you, but have you found any other way for multiple entry points. Can you also share how you do the routing worker?

MisterMard•3/8/25, 7:24 AM

Hi, I'm using the

npx wrangler pages dev

npx wrangler pages dev

command to test my angular project + backend locally.

I've set up a custom build command

ng build --output-path localdist

ng build --output-path localdist

When I run the wrangler dev command It always performs the custom build a second time after saying "The file src changed, restarting build...". Any way to prevent this from happening?

Fflashblaze I wrote a "hacky" blog post which might help you: https://flashblaze.xyz/posts/e...

Shufflepuff•3/8/25, 11:00 AM

Thanks, I'll check it out!

MMisterMard Hi, I'm using the ```npx wrangler pages dev``` command to test my angular projec...

MisterMard•3/8/25, 5:17 PM

I was able to find this https://github.com/cloudflare/workers-sdk/pull/7423 which looks like it's meant to fix, but the issue remains after testing with it. (It looks like it was possibly fixed in the first commit, then accidentally unfixed in the second commit?)

GitHub

Skip double custom build by penalosa · Pull Request #7423 · cloudfl...

Fixes #[insert GH or internal issue link(s)].
Describe your change...

Tests

TODO (before merge)
Tests included
Tests not necessary because:

E2E Tests CI Job required? (Use "e2e&am...

mihaaai•3/8/25, 6:25 PM

Is there a way to change the

.wrangler

.wrangler

artifacts on the local environment that a worker connects to?
I have 2 workers connected with service bindings, they both are connected to the same R2 Bucket but they spawn 2 different

.wrangler/state/v3

.wrangler/state/v3

in their corresponding directories, I need only one to be used and the other worker to connect to the first worker artifacts, so that when I push an object to R2 from the first, I can delete it from the second.

There was something with

getPlatformProxi()

getPlatformProxi()

but I'd like to have something configurable within

wrangler.toml

wrangler.toml

Mmihaaai Is there a way to change the `.wrangler` artifacts on the local environment that...

mihaaai•3/8/25, 6:31 PM

Never mind, just need to use the

wrangler dev --persist-to <PATH_HERE>

wrangler dev --persist-to <PATH_HERE>

but damn, it took me lots of searches to find it

verdverm.com•3/10/25, 10:46 PM

When using

wrangler dev

wrangler dev

after a build (to test prod like setup locally), is there something I need to do so that error messages use the sourcemap that sits next to

worker.js

worker.js

dipdapdop•3/11/25, 12:49 PM

Hi - I'm very new to CF Workers and Typescript development in general. I'm having an issue with a simple 3rd Party API request that I'm issuing from the Workers

fetch

fetch

handler. My sample request works fine from a simple Node env using

NodeJS.fetch

NodeJS.fetch

, but when called from the Workers

fetch

fetch

I get a

403: Forbidden

403: Forbidden

. It's a fairly old service endpoint. Can anyone suggest anything I need to take into account? [edit] I should add that this is using

wrangler dev

wrangler dev

locally to hit the

fetch

fetch

endpoint from a browser. [edit] Apologies for posting in the wrong chat.

Walshy•3/11/25, 12:55 PM

can you share your code?

dipdapdop•3/11/25, 12:59 PM

export type OAuth2TokenResponse = {
    access_token: string;
    token_type: string;
    expires_in: number;
    refresh_token: string;
    scope: string;
    created_at: number;
};

export default {
    async fetch(request, env, ctx): Promise<Response> {

        const endpoint = `${env.ETP_ROOT}/oauth/token`;

        const headers = new Headers();
        headers.append("Content-Type", "application/json");

        const raw = JSON.stringify({
            "grant_type": "password",
            "username": env.ETP_USERNAME,
            "password": env.ETP_PASSWORD,
            "client_id": env.ETP_CLIENT_ID,
            "client_secret": env.ETP_CLIENT_SECRET
        });

        const requestOptions = {
            method: "POST",
            headers: headers,
            body: raw,
            redirect: "follow"
        } as RequestInit;

        const response = await fetch(endpoint, requestOptions)

        console.log(response.status);
        const tokenResponse = await response.json() as unknown as OAuth2TokenResponse;
        console.log(JSON.stringify(tokenResponse));
        console.log(`Response token issued: expires in: ${tokenResponse.expires_in}`);
        return new Response(`Response token issued: expires in: ${tokenResponse.expires_in}`);
    },
} satisfies ExportedHandler<Env>;

export type OAuth2TokenResponse = {
    access_token: string;
    token_type: string;
    expires_in: number;
    refresh_token: string;
    scope: string;
    created_at: number;
};

export default {
    async fetch(request, env, ctx): Promise<Response> {

        const endpoint = `${env.ETP_ROOT}/oauth/token`;

        const headers = new Headers();
        headers.append("Content-Type", "application/json");

        const raw = JSON.stringify({
            "grant_type": "password",
            "username": env.ETP_USERNAME,
            "password": env.ETP_PASSWORD,
            "client_id": env.ETP_CLIENT_ID,
            "client_secret": env.ETP_CLIENT_SECRET
        });

        const requestOptions = {
            method: "POST",
            headers: headers,
            body: raw,
            redirect: "follow"
        } as RequestInit;

        const response = await fetch(endpoint, requestOptions)

        console.log(response.status);
        const tokenResponse = await response.json() as unknown as OAuth2TokenResponse;
        console.log(JSON.stringify(tokenResponse));
        console.log(`Response token issued: expires in: ${tokenResponse.expires_in}`);
        return new Response(`Response token issued: expires in: ${tokenResponse.expires_in}`);
    },
} satisfies ExportedHandler<Env>;

dipdapdop•3/11/25, 3:23 PM

@Walshy I deployed it here: https://etp-token-minimal-repro.nick-260.workers.dev/ if that is helpful.

Original message was deleted

Isaac McFadyen•3/12/25, 10:37 PM

?crossposting

SuperHelpflare•3/12/25, 10:37 PM

Please do not post your question in multiple channels/post it multiple times per the rules at #

welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.

IIsaac McFadyen ?crossposting

infiniteloop3r•3/12/25, 10:38 PM

Sorry, I'm new here!

Wonky Onion•3/13/25, 11:11 AM

Wrangler v4 has been released

You can find the changelog here https://github.com/cloudflare/workers-sdk/blob/main/packages/wrangler/CHANGELOG.md#400

try it out, and file any issues (if any!) here https://github.com/cloudflare/workers-sdk/issues

GitHub

Issues · cloudflare/workers-sdk

Home to Wrangler, the CLI for Cloudflare Workers® - Issues · cloudflare/workers-sdk

GitHub

workers-sdk/packages/wrangler/CHANGELOG.md at main · cloudflare/wor...

Home to Wrangler, the CLI for Cloudflare Workers® - cloudflare/workers-sdk

WWonky Onion Wrangler v4 has been released 🎉 You can find the changelog here https://githu...

Matt•3/13/25, 11:15 AM

Looks like the migration guide is currently 404ing

MMatt Looks like the migration guide is currently 404ing

Wonky Onion•3/13/25, 11:18 AM

just took a sec to build there

its up now!!

Fflashblaze I wrote a "hacky" blog post which might help you: https://flashblaze.xyz/posts/e...

Keebs•3/13/25, 11:27 AM

btw it’s not very obvious that those are two paths and not two steps of one path

deleted_user_3434563•3/13/25, 12:38 PM

Is there any migration guide?

Ddeleted_user_3434563 Is there any migration guide?

Peps•3/13/25, 12:54 PM

http://developers.cloudflare.com/workers/wrangler/migration/update-v3-to-v4/

Cloudflare Docs

Migrate from Wrangler v3 to v4 · Cloudflare Workers docs

Wrangler v4 is a major release focused on updates to underlying systems and dependencies, along with improvements to keep Wrangler commands consistent and clear. Unlike previous major versions of Wrangler, which were foundational rewrites and rearchitectures — Version 4 of Wrangler includes a much smaller set of changes. If you use Wrangler toda...

MMajor Tanya I was quite surprised by the now much larger worker-configuration.d.ts file sinc...

Hard@Work•3/13/25, 4:51 PM

Basically, it is dynamically generated based on your

wrangler

wrangler

config. So, instead of @cloudflare/workers-types@cloudflare/workers-types having to ship every combination of compatibility dates/compatibility flags, now you can just generate it yourself in one go

Hard@Work•3/13/25, 4:51 PM

Plus of course keeping your binding types in sync

MMajor Tanya I liked it for the Env type generation but this feels very overkill for my littl...

Hard@Work•3/13/25, 4:52 PM

I mean, the team will continue to update @cloudflare/workers-types@cloudflare/workers-types for the forseeable future, so if you don't need it, you don't have to move

Silvan•3/13/25, 4:54 PM

you arent supposed to touch that file anyway. i personally like it very much

SSilvan you arent supposed to touch that file anyway. i personally like it very much

Hard@Work•3/13/25, 4:54 PM

Yeah, I like it too, and have been using it for a few months now. But I think it's great that they give you both options

export type OAuth2TokenResponse = { access_token: string; token_type: string; expires_in: number; refresh_token: string; scope: string; created_at: number; }; export default { async fetch(request, env, ctx): Promise<Response> { const endpoint = `${env.ETP_ROOT}/oauth/token`; const headers = new Headers(); headers.append("Content-Type", "application/json"); const raw = JSON.stringify({ "grant_type": "password", "username": env.ETP_USERNAME, "password": env.ETP_PASSWORD, "client_id": env.ETP_CLIENT_ID, "client_secret": env.ETP_CLIENT_SECRET }); const requestOptions = { method: "POST", headers: headers, body: raw, redirect: "follow" } as RequestInit; const response = await fetch(endpoint, requestOptions) console.log(response.status); const tokenResponse = await response.json() as unknown as OAuth2TokenResponse; console.log(JSON.stringify(tokenResponse)); console.log(`Response token issued: expires in: ${tokenResponse.expires_in}`); return new Response(`Response token issued: expires in: ${tokenResponse.expires_in}`); }, } satisfies ExportedHandler<Env>;

in `@cloudflare/vite-plugin`'s readme i see a section titled "migrating from `wrangler dev`". now, d

Similar Threads

Similar Threads

Similar Threads