Release wrangler@4.28.0 · cloudflare/wor...
I have recently updated wrangler in my codebase from old 4.16.0 to 4.37.0 and now I am facing an annoying issue with my debug level logs fully disappeared and I genuinely think introducing it was a bad idea
I have a custom logger in my Hono application which uses env to decide the log level
Seems like after https://github.com/cloudflare/workers-sdk/releases/tag/wrangler%404.28.0 you have to specify --log-level in wrangler dev command to get debug logs
But when adding that flag, I am seeing not only app debug logs but wrangler ones as well, moreover, I can't control log level from my app config anymore AND I can't control each individual worker log level anymore
And specifying WRANGLER_LOG=info with --log-level=debug doesn't turn off wrangler excessive logs while keeping my workers logs at debug level
Maybe some solution? Apart from raising an issue
I have a custom logger in my Hono application which uses env to decide the log level
Seems like after https://github.com/cloudflare/workers-sdk/releases/tag/wrangler%404.28.0 you have to specify --log-level in wrangler dev command to get debug logs
But when adding that flag, I am seeing not only app debug logs but wrangler ones as well, moreover, I can't control log level from my app config anymore AND I can't control each individual worker log level anymore
And specifying WRANGLER_LOG=info with --log-level=debug doesn't turn off wrangler excessive logs while keeping my workers logs at debug level
Maybe some solution? Apart from raising an issue
GitHub
Minor Changes
#9530 e82aa19 Thanks @Akshit222! - Add --json flag to r2 bucket info command for machine-readable output.
Patch Changes
#10004 b4d1373 Thanks @dario-piotrowicz! - fix wrangler dev...
#9530 e82aa19 Thanks @Akshit222! - Add --json flag to r2 bucket info command for machine-readable output.
Patch Changes
#10004 b4d1373 Thanks @dario-piotrowicz! - fix wrangler dev...
