ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #denojs
Master Deno’s permission system—control file reads, network calls, and env vars on a per‑file basis. Walk through real commands, trade‑offs, and how to verify your own scripts.
Learn how to apply Deno’s capability‑based permission model to grant a service only the filesystem and network access it truly needs, with concrete flags, runtime checks, and failure‑mode analysis.
An architecture note covering Deno’s permission system: requirements, minimal design, trust boundaries, operational checks, failure modes, and when the design would change.
Stop using blanket --allow-read flags. Learn how to use Deno's granular permission system to implement the principle of least privilege and secure your scripts.
Learn how Deno's capability-based security model replaces implicit trust with explicit permissions for network, file system, and environment access to mitigate security risks.
Stop fighting with tsc and node_modules. Learn how Deno's native TypeScript execution and secure-by-default sandbox eliminate the build step for modern TS development.
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
Resource Management at the Runtime Boundary Deno manages memory via the V8 engine's garbage collector, but external resources—such as those handled through the internal Ops layer—require precise cleanup to avoid memory leaks in the native layer. While FinalizationRegistry is used to schedule the release of these external resources when the corresponding Java
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
javascript