--env staging, and it wasn't finding my env for some reason. and it turns out, it's because there's this file being written to .wrangler/deploy/config.json that has these contents: which points to build/server/wrangler.json being written during the build process, which is a stripped down version of my wranger.jsonc. what's going on here???wrangler dev use my system environment variables? It doesn't pull them automatically, I have to list them in .dev.vars, and I'd like to avoid that.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?node_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?nodejs_compat, not node_compat, right?nodejs_compat to my config, which is already there."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.workerd. workerd does run in production, but the goal is for you to never need to care which version of workerd is runningBuffer?nodejs_compat


@cloudflare/workers-types , but get incompabilities when e.g. upgrading wrangler--env staging.wrangler/deploy/config.json{"configPath":"../../build/server/wrangler.json","auxiliaryWorkers":[]}%wranger.jsoncnpm 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_compatdev.tomlwrangler.toml