It looks like you just have a generic `node-gyp` issue
It looks like you just have a generic
node-gyp issuenode_modules/wrangler/node_modules/better-sqlite3python3 installed and available - if you run it via terminal, it should enter into a python promptnpx wrangler deploy --dry-run --outdir dist --minify=true or npx wrangler deploy --dry-run --outdir dist I can clearly identify dead code that isn't needed for the worker. I've set all my ts modules to "esnext", but still no good. I also don't see any way to adust the esbuild config. Any suggestions?... right in the middle. I don't think it is related to nested objects, but could benpm run build:watch and npm run wrangler in 2 terminals. The first one build the app and create an empty .trigger file in the working directory. The other one watches for .trigger files (made up extension) and restarts wrangler then delete the .trigger file.
https://discord.gg/cloudflaredev?event=1133767196494008442wrangler pages dev --d1=<your d1> --remotepages dev doesn't support --remote unfortunatelydev (not pages) which is probably what you're thinking about --local=falseconsole.log(JSON.stringify(authObject));{"adapter":{},"sessionCookie":{"name":"auth_sessio…ubdomains":[],"experimental":{"debugMode":false}}// package.json
"scripts": {
"build:watch": "nodemon --watch src -e ts,svelte --exec \"vite build; touch reload.trigger\"",
"wrangler": "nodemon -e trigger --exec \"rm reload.trigger; wrangler pages dev .svelte-kit/cloudflare \""
},pages dev--local=false