Yeah, looks like something the React dev server is returning breaks GZip...
Yeah, looks like something the React dev server is returning breaks GZip...
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.workerd doesn't support that architecture, correctdeploy 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.npm i (or the equivalent in the package manager you're using) in CI already?preCommands: npm install should be all you need I supposewith block - put it before command (just aesthetics)npm ci over npm install if you have a lockfile, for stable and reproducible builds, but yep, preCommands is great for that devDependencies is fine and what I'd recommend for something like this. But it won't matter here@cloudflare/workers-types and typescript could probably be devDependencies I guessdependencies 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.devDependencies, but you're not publishing to npm... so it doesn't overly matter.sudo npm install -g wrangler but getting the following starting error: