H
NN
E
F
J
M
IMMMI
M
node_compat to nodejs_compat. Should I do this not only in my dev.toml but also wrangler.toml i.e. the TOML for the production version? Does production always use the latest Wrangler?Mnode_compat. But a previous message told me to change node_compat to nodejs_compat for use with v.4, which I did. What am I doing wrong?Mnodejs_compat, not node_compat, right?Mnodejs_compat to my config, which is already there.M"Unexpected fields found in top-level field: "nodejs_compat"So I have messages telling me both to add
nodejs_compat and also that nodejs_compat is invalid.MM
HMMHworkerd. workerd does run in production, but the goal is for you to never need to care which version of workerd is running
NBuffer?
JJnodejs_compatN
NNN
NNN
II
J
Now when wrangler@4 generates all the types, does anyone have guidance as to how to build libraries that depend on e.g. D1Database? For https://github.com/jonasb/d1-sql-tag I'm using @cloudflare/workers-types , but get incompabilities when e.g. upgrading wrangler
M
EEinterface Env extends Cloudflare.Env {}. On further inspection, its when there's a durable object namespace in the types, it doesn't resolve (I'd removed the types to keep it short for this example and it worked). But it's completely fine if the type isn't extended
E ORGANISATION_PERFORMANCE_REPORT: DurableObjectNamespace<import("./workers/app").organisationPerformanceReportDO>;). 
E
T
npm install --save-dev wrangler@4`npm ERR! code EINVALIDTAGNAME
npm ERR! Invalid tag name "4`" of package "wrangler@4`": Tags may not have any characters that encodeURIComponent encodes.node_compatnode_compatnode_compatnode_compatnodejs_compatnodejs_compatnodejs_compatnodejs_compatnodejs_compatnodejs_compatnodejs_compatdev.tomlwrangler.tomlworkerdworkerdworkerdBuffer@cloudflare/workers-typesinterface Env extends Cloudflare.Env {} ORGANISATION_PERFORMANCE_REPORT: DurableObjectNamespace<import("./workers/app").organisationPerformanceReportDO>;