downgrade your Wrangler version to 3.61.0 or less and use wrangler dev (or wrangler commands)
downgrade your Wrangler version to 3.61.0 or less
and use wrangler dev (or wrangler commands)
and use wrangler dev (or wrangler commands)
Bis there a way to have one "global" wrangler.toml file? I have a monorepo with a bunch of packages that need to access the same db, and I am trying to work through the best way to do that.
KMiniflare is a standalone library, you can't run it in
wrangler devwrangler dev
JWhat's the
wranglerpackage.jsonnpxnpx wrangler@3.63.1 devJIf you're creating a new project, I'd definitely recommend
npm create cloudflare@latest: https://developers.cloudflare.com/workers/get-started/guide/Cloudflare Docs
Set up and deploy your first Worker with Wrangler, the Cloudflare Developer Platform CLI.
JCan you share your repository/config?
JIf this is a new project, I'd again heavily encourage you to start over with
npm create cloudflare@latest. That'll ensure you get all the right dependencies and thingsJThat should be fine. Can you share the script you're trying to run and a full error log please?
JIs your intent to use
miniflarewrangler devnodeIf you
npm create cloudflare@latest, it'll give you a basic foundation script and a dev script you can run via npm run devYou can't run
Miniflare like that via wrangler devwranglerYou could use miniflare for that like what you have, but you'd run it via
nodewranglerYeah, that won't work, miniflare doesn't have a CLI anymore. And your script isn't a workers script that works this way.
JYou could probably run your code via
nodehappy to help 
AThis doesn't seem right, does it?
AThis is all my dev script is doing:
And yet, after a few days, i end up with tons of these processes. After clearing them, running dev starts two workerd processes. If i kill the server, they exist cleanly, so the happy path is clean
"dev": "NODE_ENV=development wrangler dev -e dev src/index.ts",And yet, after a few days, i end up with tons of these processes. After clearing them, running dev starts two workerd processes. If i kill the server, they exist cleanly, so the happy path is clean
SHey! Has anyone experienced CORS policy issue as of
wrangler 3.62localhostwrangler: 3.00no-cors
Ai was facing an issue deploying a worker to dispatch namespace. with durable object bindings and migrations. it worked fine for the first time (i.e creating the script for the first time). but it always failed after that ~
i have submitted a pr that aims to potentially fix this issue https://github.com/cloudflare/workers-sdk/pull/6246
i have submitted a pr that aims to potentially fix this issue https://github.com/cloudflare/workers-sdk/pull/6246
GitHub
What this PR solves / how to test
This PR addresses an issue where deploying a worker to dispatch namespaces would fail due to the way Wrangler retrieves migrations from the script. Although this P...
This PR addresses an issue where deploying a worker to dispatch namespaces would fail due to the way Wrangler retrieves migrations from the script. Although this P...
SShould be fine
Afaced the same problem in 3.61.0 as well
Mhello, I have created new cloudflare app. after installing when i ran the command
error:
npm run dev npm starterror:
Mnpm run deploy 
JDoes
I'm trying to access RPCs from a worker in a pages project, and I'm using
However, when trying to call an RPC on a bound service, I get the following error:
If I call the RPC from a regular workers project it works just fine.
Wrangler version 3.65.0
getPlatformProxyI'm trying to access RPCs from a worker in a pages project, and I'm using
getPlatformProxyHowever, when trying to call an RPC on a bound service, I get the following error:
If I call the RPC from a regular workers project it works just fine.
Wrangler version 3.65.0
JThe above error is from this code snippet
DgetPlatformProxy
I think this is blowing up in the Miniflare magic proxy as the code is trying to send some non serializable object across the wire (the error message comes from devalue which the magic proxy uses to serialize values: https://github.com/Rich-Harris/devalue/blob/0c35c0e7a6a37172c7f049eaae4e7079559ba250/src/stringify.js#L149)
@Jakob Norlin would you be able to spin up a minimal reproduction of the issue?
(if you want please feel free to create a workers-sdk issue and tag me there: https://github.com/cloudflare/workers-sdk/issues/new/choose)
GitHub
Gets the job done when JSON.stringify can't. Contribute to Rich-Harris/devalue development by creating an account on GitHub.
GitHub
Home to Wrangler, the CLI for Cloudflare Workers® - cloudflare/workers-sdk
Home to Wrangler, the CLI for Cloudflare Workers® - cloudflare/workers-sdk
JHere's the minimal repro: https://github.com/jakst/wrangler-rpc-platform-proxy. I'll create an issue in a sec
JGitHub
Which Cloudflare product(s) does this pertain to? Wrangler, Miniflare What version(s) of the tool(s) are you using? 3.65.o [wrangler] What version of Node are you using? 22.4.1 What operating syste...
Doh.... wow this is very very basic... I was hoping that you might have been doing something specific on your side that was causing the issue... bizarre.... I now wonder if the workers-sdk tests are actually running!
Danyways thanks so much this is great! 
