New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open

canadaduane opened this issue Nov 21, 2024 · 0 comments

canadaduane commented Nov 21, 2024

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.

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment