I've opened an enterprise chat request, will update here when I hear something.
I've opened an enterprise chat request, will update here when I hear something.



wrangler types becoming more cohesive with @types/node? All the time the typegen doesn't actually match runtime behaviour here and include real nodejs_compat types, it just causes more problems in my experience, especially when you introduce third party libs that still have to use workers-types.
CLOUDFLARE_ACCOUNT_ID work?vite dev. The problem is that this worker is a "child" binding in a parent router, and when it starts up, the parent wrangler dev does not see it. Is there any way to get this working?
{
"name": "router",
"main": "apps/dev-router/src/index.ts",
"compatibility_date": "2025-04-03",
"workers": {
"dash": "apps/dash/wrangler.jsonc",
"api": "apps/server/wrangler.jsonc"
},
"services": [
{
"binding": "DASHBOARD_SERVICE",
"service": "dash"
},
{
"binding": "API_SERVICE",
"service": "api"
}
],
"dev": {
"port": 8080,
"local_protocol": "http"
}
} ERROR dyld[87080]: Symbol not found: (__ZNSt3__122__libcpp_verbose_abortEPKcz)
ERROR Referenced from: '/Users/x/dev/app/node_modules/@cloudflare/workerd-darwin-64/bin/workerd'
ERROR Expected in: '/usr/lib/libc++.1.dylib'
ERROR Failed to initialize wrangler bindings proxy write EPIPE