Hardening Deno Scripts with Granular Permission Flags
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.
Loading…
ReadMeFeed / Community knowledge
#deno
Real questions. Useful conversations. Find the people who know your stack.
Reducing Latency with Netlify Edge Functions: When to Move Logic to the Edge
Learn how to use Netlify Edge Functions to reduce latency by moving request logic—like A/B testing and geo-redirects—closer to your users using the Deno runtime.
netlifyArchitecting Secure Runtimes with Deno's Capability-Based Permissions
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.
javascriptSimplifying the TS Toolchain: Running TypeScript Without a Build Step
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.
Deno Runtime and V8 FinalizationRegistry: External Resource Cleanup Timing
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
Does deno upgrade provide automatic rollback on failure?
The deno upgrade command replaces the current Deno executable with a newer version. While the process typically involves downloading a binary and replacing the existing file, the behavior during a catastrophic failure—such as a system crash or an interrupted write—is not explicitly defined as a self-healing process. On Unix-like systems, the rename operation
Deno long-running process retains stale DNS entries beyond TTL
Goal Determine whether Deno's DNS resolution cache in long-running server processes respects record TTL values or retains entries indefinitely. Constraints and uncertainty Deno's underlying Rust networking stack manages DNS caching, but cache duration is not consistently documented across Deno APIs. Behavior may differ between Deno versions due to Rust imple
Behavior of TLS session cache release when custom root certificates are supplied via --allow-net
When running a Deno HTTP server with the --allow-net flag and providing custom root certificates, it is unclear whether Deno actively releases or reuses TLS session caches after connections close. The goal is to determine if the TLS session cache is retained for the lifetime of the process, flushed periodically, or tied to the lifecycle of individual sockets
Lock File Auto‑Update vs. Manual Locking: Trade‑off for Deterministic Deno Builds
Goal: achieve a repeatable Deno development environment that guarantees the same dependency versions across machines and CI runs while minimizing manual overhead. Constraint: teams can either rely on Deno to automatically refresh deno.lock on every execution or maintain a static lock file that is updated only via an explicit deno cache --lock step; the forme