MMitya Anyone from CF able to comment/help here?

C

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

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

Z

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

H

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

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

Z

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

okey ty

K

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...

A

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?

M

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...

S

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...

M

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...

M

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...

M

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

V

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

?

D

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.

W

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

can you share your code?

D

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>;

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>;

D

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

I

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

?crossposting

S

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

I

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

Sorry, I'm new here!

W

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...

M

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

Looks like the migration guide is currently 404ing

MMatt Looks like the migration guide is currently 404ing

W

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...

K

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

D

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

Is there any migration guide?

Ddeleted_user_3434563 Is there any migration guide?

P

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...

H

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

H

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...

H

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

S

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

H

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

S

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

for sure!

S

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

loc are a lie

but yea importing from cf-types/compDate is fine too

MMajor Tanya I mean I wouldn't touch the file in either case but this file has doubled the lo...

H

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

I mean, theoretically Workers Types(the Package) is actually larger, it just doesn't count as LoC because it is gitignored

A

ashutosh•3/13/25, 8:27 PM

https://developers.cloudflare.com/workers/wrangler/system-environment-variables/

This page over here says the

CLOUDFLARE_API_TOKEN

CLOUDFLARE_API_TOKEN

can be used. But if I use the variable then I get an error as

✘ [ERROR] You are logged in with an API Token. Unset the CLOUDFLARE_API_TOKEN in the environment to log in via OAuth.

✘ [ERROR] You are logged in with an API Token. Unset the CLOUDFLARE_API_TOKEN in the environment to log in via OAuth.

Okay, now if I try to login with OAuth, the page freezes because the IP was blocked.

The IP was blocked because I was using service like Github Workspace.

Wrangler 4 is a mess and seriously stopping me work with Cloudflare Infrastructure. Can someone have a look and clear the things up?

What is the reason that a person cannot login with API_TOKEN? If you guys are blocking logging in with API_TOKEN, how

wrangler

wrangler

commands are supposed to work in CI environments?

This is seriously a frustruating experience.

Cloudflare Docs

System environment variables · Cloudflare Workers docs

Local environment variables that can change Wrangler's behavior.

Aashutosh https://developers.cloudflare.com/workers/wrangler/system-environment-variables/...

I

Isaac McFadyen•3/13/25, 8:51 PM

What command are you running that is rejecting CLOUDFLARE_API_TOKEN?

IIsaac McFadyen What command are you running that is rejecting CLOUDFLARE_API_TOKEN?

A

ashutosh•3/13/25, 9:32 PM

I used to work this way with

wrangler dev

wrangler dev

and

wrangler dev --remote

wrangler dev --remote

But none of the commands are working including

wrangler deploy

wrangler deploy

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

W

Wonky Onion•3/13/25, 10:06 PM

You can also just pass in —include-runtime=false and you’ll get just the Env types like before, if you prefer :)

V

VeriHappy•3/14/25, 1:19 AM

when i try to update my wrangler i get an error thats "unfixable" and so now i cant update my wrangler

Ppenalosa What error are you seeing?

V

VeriHappy•3/14/25, 2:01 AM

a big text says "▲ [WARNING] The version of Wrangler you are using is now out-of-date.

Please update to the latest version to prevent critical errors.
Run

npm install --save-dev wrangler@4

npm install --save-dev wrangler@4

to update to the latest version.
After installation, run Wrangler with

npx wrangler

npx wrangler

."

but when i run npm install --save-dev wrangler@4 i get this

up to date, audited 141 packages in 3s

19 packages are looking for funding
run

npm fund

npm fund

for details

5 vulnerabilities (3 low, 2 moderate)

Some issues need review, and may require choosing
a different dependency.

Run

npm audit

npm audit

for details.

so i run npm audit to see whats going on and i get this

npm audit report

cookie <0.7.0
cookie accepts cookie name, path, and domain with out of bounds characters - https://github.com/advisories/GHSA-pxg6-pf52-xh8x
No fix available
node_modules/youch/node_modules/cookie
youch 2.0.4 - 3.3.3
Depends on vulnerable versions of cookie
node_modules/youch
miniflare <=0.0.0-fff677e35 >=3.20250204.0
Depends on vulnerable versions of youch
node_modules/miniflare
wrangler *
Depends on vulnerable versions of esbuild
Depends on vulnerable versions of miniflare
node_modules/wrangler

esbuild <=0.24.2
Severity: moderate
esbuild enables any website to send any requests to the development server and read the response - https://github.com/advisories/GHSA-67mh-4wv8-2f99
No fix available
node_modules/esbuild

5 vulnerabilities (3 low, 2 moderate)

Some issues need review, and may require choosing
a different dependency.

GitHub

CVE-2024-47764 - GitHub Advisory Database

cookie accepts cookie name, path, and domain with out of bounds characters

GitHub

GHSA-67mh-4wv8-2f99 - GitHub Advisory Database

esbuild enables any website to send any requests to the development server and read the response

V

VeriHappy•3/14/25, 2:07 AM

(nvm i fixed it)

V

VeriHappy•3/14/25, 2:07 AM

i did

npm update -g wrangler

npm update -g wrangler

Ppenalosa To clarify, were these commands working with Wrangler v3?

A

ashutosh•3/14/25, 5:34 AM

I started getting this error about 1 or 2 week ago. I assumed that it was due to updated version or wrangler but now when I tried it with lower version of wrangler (i.e.

3.93.0

3.93.0

), I am still getting the same error which probably means there was some change in the Cloudflare APIs which is causing this issue.

A

ashutosh•3/14/25, 5:37 AM

Getting this error with all the versions of wrangler (probably) while logging in with OAuth.

Screenshot_2025-03-14_at_11.06.43_AM.png

Anyone from CF able to comment/help here?

npm audit report

Similar Threads

Similar Threads

npm audit report

Similar Threads