Wrangler: fix console.debug
logs not being logged at the info
level (as users expect)
#10757
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #10690
The changes in #10004 made sure that wrangler prints logs at the correct log level.
This however caused
console.debug
logs not to be printed anymore at the default info level. Users also cannot get their debug logs (via--log-level=debug
) without also getting all the noisy Wrangler logs.So it's been decided that for the time being wrangler should log
console.debug
logs at the info level so that users keep getting them as they are used to. Then in the next major wrangler release we should update wrangler to print those logs in the debug level instead but also introduce some mechanism for allowing users to opt-out/in to the wrangler noisy debug logs.