🐛 BUG: pages dev output is unnecessarily verbose

[Cherry]

Which Cloudflare product(s) does this pertain to?

Pages, Wrangler core

What version(s) of the tool(s) are you using?

3.14.0

What version of Node are you using?

18.18.0

What operating system are you using?

Windows

Describe the Bug

When running npx wrangler pages dev <dir>, you get a LOT of verbose output:

> npx wrangler pages dev ./dist

▲ [WARNING] No compatibility_date was specified. Using today's date: 2023-10-23.

  Pass it in your terminal:
  \`\`\`
  --compatibility-date=2023-10-23
  \`\`\`
  See https://developers.cloudflare.com/workers/platform/compatibility-dates/ for more information.


Compiling worker to "C:\Users\james\AppData\Local\Temp\functionsWorker-0.005178014829587907.mjs"...
✨ Compiled Worker successfully
 ⛅️ wrangler 3.14.0
-------------------
▲ [WARNING] --local is no longer required and will be removed in a future version.

  `wrangler dev` now uses the local Cloudflare Workers runtime by default. 🎉


⎔ Starting local server...
▲ [WARNING] Parsed 5 valid header rules.


[mf:wrn] The latest compatibility date supported by the installed Cloudflare Workers Runtime is "2023-10-16",
but you've requested "2023-10-23". Falling back to "2023-10-16"...
kj/async-io-win32.c++:982: warning: Bind address resolved to multiple addresses.  Only the first address will be used.  If this is incorrect, specify the address numerically.  This may be fixed in the future.; addrs[0].toString() = 127.0.0.1:59452
[mf:inf] Ready on http://0.0.0.0:8788
[mf:inf] - http://172.22.208.1:8788
[mf:inf] - http://192.168.50.240:8788
[mf:inf] - http://127.0.0.1:8788

That's a lot of visual noise to try and scan and determine if my command was successful or not.

This is without any wrangler.toml in my directory.

Actionable things I'd recommend:

• Reduce compat date warnings. Improved in [wrangler] Clean up compatibility fallback warnings #4209
• Remove --local warning - pages dev is ONLY local and I didn't even pass this. I suspect it's coming from unstable_dev: fix: remove confusing --local messaging from wrangler pages dev #4687
• Remove "warnings" for valid header rules
• Remove workerd startup warnings with multiple networks in windows: 🐛 BUG: warning always received about multiple bind addresses workerd#1408

[klaemo]

I can confirm this and it's still like that in 3.15.0

npx wrangler pages dev dist                                
▲ [WARNING] No compatibility_date was specified. Using today's date: 2023-11-09.

  Pass it in your terminal:
  \```
  --compatibility-date=2023-11-09
  \```
  See https://developers.cloudflare.com/workers/platform/compatibility-dates/ for more
  information.


Compiling worker to "/Users/clemens/Projects/webapp/.wrangler/tmp/pages-10DKtg/functionsWorker-0.21075951104789326.mjs"...
✨ Compiled Worker successfully
 ⛅️ wrangler 3.15.0
-------------------
▲ [WARNING] --local is no longer required and will be removed in a future version.

  `wrangler dev` now uses the local Cloudflare Workers runtime by default. 🎉


Using vars defined in .dev.vars
Your worker has access to the following bindings:
- Vars:
  - API_URL: "(hidden)"
⎔ Starting local server...
▲ [WARNING] Parsed 1 valid redirect rule.


▲ [WARNING] Parsed 3 valid header rules.

There are just way too many warnings for a successful operation

• the compatibility-date warning is confusing. If I'm required to pass this, why is it an optional flag?
• the warning about --local is just plain wrong, because I didn't pass that flag
• the warnings about valid header and redirect rules prompted me to check if I did something wrong...but apparently not

I think a one liner log message for the successful start of the local server would be sufficient. Something like:

Started local server on http://0.0.0.0:8788 with 1 redirect rule, 3 header rules and compatibility-date=2023-11-09.

or if you want to to be slightly more verbose:

Local server listing on http://0.0.0.0:8788
- detected 1 redirect rule
- detected 3 header rules
- using compatibility date "2023-11-09"

[newsve]

It gets worse if you use something like Vite, then you see thousands of urls on every request to the dev servers and can't catch any of our own console.logs anymore

[CarmenPopoviciu]

triaging this as part of https://github.com/cloudflare/workers-sdk/milestone/10 and will discuss with the team if this is something we can take on as part of that body of work

[treeder]

I'm with @newsve , can we silence the request log messages? I only want to see what I'm logging. Or perhaps a --verbose option to see every single request. This is what happens now, hundreds of request logs making it hard to find the important stuff:

[CarmenPopoviciu]

Hi folks,

First of all, thank you for raising this issue, and for providing us will the information you did <3!

As we are picking this up as part of https://github.com/cloudflare/workers-sdk/milestone/10, I just want to confirm the current state of affairs, as codebase has evolved since this issue was first reported.

Running wrangler pages dev [directory] in wrangler version 3.57.0, in a Pages project with:

• Functions
• _routes.json
• _headers
• _redirects
• no wrangler.toml file

currently outputs the following (pls correct me in case I missed anything):

In the original report by @Cherry, the suggested actionable items were:

• Reduce compat date warnings. [Applicable]
• Remove --local warning - pages dev is ONLY local and I didn't even pass this. [N/A as these warnings were already removed]
• Remove "warnings" for valid header rules. [N/A as these were converted to logs instead of warnings, but please see my followup question below]
• Remove workerd startup warnings with multiple networks in windows. [TBD? will need to repro, but wondering if folks are still experiencing this?]

Subsequent reports also suggested to

• Silence the request log messages [TBD as this is not pages specific, but is output by both wrangler dev and wrangler pages dev]

// "wrangler dev" output

In addition to what was already suggested in these discussions, I'm wondering if logs such as:

• Compiling worker to "/.../pages-functions-with-routes-app/.wrangler/tmp/pages-IIkQRR/functionsWorker-0.6251491221119416.mjs"...
• Parsed 1 valid redirect rule.
• Parsed 1 valid header rule.

are helpful or become noise? Do you have any input on that?

[Cherry]

Personally, I think most of my original issues with the verbosity of this have since been resolved.

The compatibility date warning is a bit noisy when you don't specify one (and should maybe recommend wrangler.toml now instead?), but at least you don't get one now from both pages dev, and miniflare.

And then the "Compiling worker" line is a little verbose and unnecessary, but everything else is useful information now I think.

[CarmenPopoviciu]

I abs agree with you @Cherry that compat date and fns compilation output is noisy. I'll add fixes for both, plus some extra things to make the output more readable and more organised and circle back here.

IMHO, our stdout formatting in general could use some more structure and consistency, but not sure if there was ever time to properly address this. I'll see if there's smth we can do abt that as well, but that's for later.

In the meanwhile anyone interested in the changes related to this issue can follow the progress over at #5927