Cloudflare Developers

CD

Cloudflare Developers

Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news

Join

Hey,

Hey, I'm trying to use github action to deploy our worker, using cloudflare/wrangler-action@v3. This is my yml file: ``` name: Deploy Worker...

No such module "wrangler:modules-watch"

Anyone seen this before? No such module "wrangler:modules-watch" ``` ⎔ Starting local server... [wrangler:inf] Ready on http://localhost:5010 ✘ [ERROR] service core:user:phosphor-server: Uncaught Error: No such module "wrangler:modules-watch"....
No description

`wrangler pages dev` hangs on macOS + bun

Has anyone seen an issue where wrangler pages dev doesn't start the server unless you restart your computer (macOS arm, bun)? It also hangs when you try to shut down the server ```toml #:schema node_modules/wrangler/config-schema.json name = "phosphor-server"...
No description

Good to hear! Looking forward to the

Good to hear! Looking forward to the results 🙂

Can I refer to env vars in wrangler.toml

Can I refer to env vars in wrangler.toml? I am setting up inngest with Cloudflare and need to set INNGEST_SIGNING_KEY, technically that's a "secret" but setting it via wrangler secret put INNGEST_SIGNING_KEY doesn't make it available in the "environment variables", inngest sync fails and to put it in environment variables, I need to add it to wrangler.toml as "plain text" and deploy.

Whenever I run `dev`, the process

Whenever I run dev, the process oftentimes doesn't shut down correctly and it ends up needing to use a different port every time. I get errors like this: ✘ [ERROR] Address already in use (127.0.0.1:60392). Please check that you are not already running a server on this address or specify a different port with --port. So I have to run the following:...

For some feedback (not a bug), since

For some feedback (not a bug), since wrangler 'lost' the capability to 'port forward' a dev server, it's been a nightmare to develop a Pages project with Functions... Regular pages: just ignore wrangler and use 'bun run dev' or whatever you're using; it'll update automatically on file save; Regular Worker: same thing, just run with wrangler and it'll auto-detects changes automatically and reload;...

what does the new dev env bring

what does the new dev env bring

it's working for me. but still debugger

it's working for me. but still debugger doesn't work, that's the one thing i want fixed 😬 https://github.com/cloudflare/workers-sdk/issues/5339#issuecomment-2189587023

So wrangler just made me go through the

So wrangler just made me go through the oauth process again, but now when I click Allow, wrangler throws an error. SyntaxError: Unexpected token < in JSON at position 0

Hey wrangler team... this is a crosspost

Hey wrangler team... this is a crosspost from the DO channel, but I'm not getting responses there, and it may be a wrangler issue anyway: I'm trying to republish an updated itty-durable that imports/extends { DurableObject } from 'cloudflare:workers'... This works fine, and folks can use it downstream as long as they are using wrangler (obv), but I am unsure of how to add test coverage to this in a way that'll pass outside of a wrangler environment (e.g. jest/vitest on GH actions)....

@Cloudflare (Server Owner) is anyone

@Cloudflare (Server Owner) is anyone else having this problem?

Is anyone having failures with `npx

Is anyone having failures with npx wrangler login today? It was working fine yesterday, but dtoday I'm getting a non-json response back from the API SyntaxError: Unexpected token < in JSON at position 0

nvm I figured it out after running

nvm I figured it out after running wrangler pages download config <PROJECT> and looking at how the generated config is setup. The service bindings should be in the production environment. The docs aren't clear about this and there aren't really any error messages during deployment ```toml [env.production] compatibility_date = "2024-04-06"...

Not sure if this is a #wrangler or #

Not sure if this is a #wrangler or #miniflare issue, but the following code will throw in wrangler dev (ignored/safe in production): Error Reproduction ```ts export default {...

I'm trying to get my local d1 database

I'm trying to get my local d1 database from one local project to another local project, i.e., from one dir to another dir without re-running the wrangler d1 execute --local --file=.sql approach. I thought I could just move the .wrangler/state/v3/d1 dir over to another dir and spin things up but that did not work. Is there some other approach I could use? My problem is that I use a separate worker to load portions of the database and I was hoping to avoid moving that worker and its config over to another dir temporarily to get the database fully loaded. Thanks!...

Is it possible to configure wrangler to

Is it possible to configure wrangler to open something other than localhost when working locally? [wrangler:inf] Ready on http://localhost:8788, I'd like it to open a local alias instead of localhost but still maintain the protocol and port, e.g., http://<local-alias>:8788... it's mainly to get around CORS stuff 🙄...

That sounds like you have a library

That sounds like you have a library which is trying to use an unsupported field (credentials). Whilst browsers support that, Workers don't.