platform · inferred from evidence
Deno Deploy
A platform for deploying Deno applications.
- Deno Deploy: Oak shows "[uncaught application error]: UnexpectedEof - early eof" after idle
This happened because Deno Deploy shuts down the idle isolate and hard-closes the listening socket, which Oak surfaced as an uncaught UnexpectedEof error. Deno rolled out a platform change on Dec 7, 2022 to stop these logs from being emitte
- Deno Deploy: Deno.env.get() returns undefined at module top level (env vars not read)
On Deno Deploy, dashboard environment variables are not reliably available when top-level module code runs — move any Deno.env.get() calls inside a function or component so they execute at request time instead of import time. The reporter c
- Deno Deploy: "Unexpected non-whitespace character after JSON at position 3" when fetching own API (508 loop)
The JSON parse error was a red herring: the real problem was the 508 status, which Deno Deploy returns when it detects a request loop — a deployment making an HTTP request to itself. Deno Deploy blocks recursive requests where deployment A
- Deno Deploy: "Queues not available on preview environment" error in production right after deploy
This was a platform-side race in how Deno Deploy classified a fresh deployment's environment. Right after a production deploy, the new isolate could briefly be treated as a preview environment, so Deno Queues refused to run and in some case