H
HH
S
npm run pages:dev which in turn runs wrangler pages dev --compatibility-date=2023-06-18 --proxy 5173 -- npm run dev. This triggers an oauth login to cloudflare in the browser. Out of interest, why? Given it's running locally with Wranger v3.
Kworkerddeploywrangler deploy --var GOVEE_API_KEY:$WRANGLER_GOVEE_API_KEY but those are plain-text in the dashboard & whatnot so ideally you'd use secrets.K
DKnpm ipreCommands: npm install should be all you need I supposeKwith block - put it before command (just aesthetics)
Jnpm ci over npm installpreCommands is great for that 
JdevDependencies is fine and what I'd recommend for something like this. But it won't matter hereK@cloudflare/workers-types and typescript could probably be devDependencies I guessJdependencies are for runtime things, if you've got an app that runs and uses express for example.devDependencies for dev tooling, or anything that's only used to build, like everything here, since it's all bundled into a single output worker.DJDJ
devDependencies, but you're not publishing to npm... so it doesn't overly matter.JKJ
Csudo npm install -g wrangler but getting the following starting error:Cnpm run pages:devwrangler pages dev --compatibility-date=2023-06-18 --proxy 5173 -- npm run devwrangler deploy --var GOVEE_API_KEY:$WRANGLER_GOVEE_API_KEYpreCommands: npm installwithcommandnpm cipreCommandsdevDependenciesdevDependenciesdevDependencies@cloudflare/workers-typestypescriptdependenciesexpresssudo npm install -g wrangler