Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
83,498Members
View on DiscordResources
Similar Threads
Was this page helpful?
HH
HHHHHHH
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.
Kworkerddeploy like wrangler 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 i (or the equivalent in the package manager you're using) in CI already?KpreCommands: npm install should be all you need I supposeKwithcommand (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 typescriptdependenciesexpress 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.JKnpm run pages:devwrangler pages dev --compatibility-date=2023-06-18 --proxy 5173 -- npm run devdeploywrangler deploy --var GOVEE_API_KEY:$WRANGLER_GOVEE_API_KEYnpm ipreCommands: npm installcommandnpm cipreCommandsdevDependenciesdevDependenciesdevDependencies@cloudflare/workers-typesexpress