Adding DENO_DEPLOYMENT_ID to .env silences "Fresh ready" listen message

[canadaduane]

This was very confusing / unintuitive for me:

• several days ago, I added "DENO_DEPLOYMENT_ID" to my local .env file
• I added the --env-file=.env flag to the dev task recently
• whenever I tried to start Fresh, it appeared to "hang"

Slightly irrelevant, but nevertheless confusing: When I tried to debug with --inspect-wait, I was additionally greeted with a deno core panic.

Anyway, I think it's unintuitive that the presence of a DENO_DEPLOYMENT_ID key should suppress the "Fresh ready" message in development.

[marvinhagemeister]

This is resolved in recent alpha version of Fresh 2. There we use deno serve which always prints a "listening" message in a single line.