ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #denojs
I am building a Deno application that uses the standard logging module (std/log) to output diagnostic information. I want the console to show only warnings and errors so that informational messages do not create noise during development, while still retaining a complete log file that records every level, including debug and info, for later analysis. The appl
A design needs to write a single output file with automatic retries and avoid duplicated or partial writes when multiple invocations overlap. The constraint is cross-platform consistency and no built-in atomic-write helper in the Deno standard library. One documented approach is write-to-temp then Deno.rename. On POSIX systems rename is commonly atomic, whic
Context Deno caches all remote modules under DENO_DIR and reuses them across runs unless a module hash changes or --reload is supplied. The cache does not automatically invalidate based on time or upstream modifications. Goal Ensure that a script always executes with the current version of its remote dependencies without requiring manual intervention before
Handling Request Payloads with ReadableStreams The Deno.serve() API utilizes the Web Standard Fetch API, allowing handlers to process incoming Request objects. For large payloads, Deno leverages ReadableStream to maintain memory efficiency by avoiding the buffering of the entire request body into memory. When integrating custom middleware or multiple process
Deno's permission system requires explicit flags at startup, but also offers runtime requests via Deno.permissions.request() , which triggers a user prompt in interactive terminals. In non‑interactive CI or Docker environments, the lack of a TTY causes the process to hang or fail because the prompt cannot be answered. Current workarounds such as --allow-all
Dependency Pinning in Deno Deno ensures repeatable development environments by utilizing a lock file to pin remote module dependencies to specific checksums. This mechanism prevents environment drift when multiple developers or CI pipelines resolve the same import map specifiers. Configuration Transition Recent updates to the runtime have introduced a transi
Goal: Cost‑Effective Low‑Traffic Deployments For workloads that run infrequently, limiting network access can reduce the attack surface and simplify compliance. However, Deno’s current permission system requires explicit host names for each --allow-net grant, which can become burdensome when the set of external services changes. Constraint: No Wildcard or Re