Controlling Deno File System Access with Permission Flags
Learn how to grant Deno scripts precise file‑system access with --allow-read and --allow-write flags, see a concrete example, and understand the limits and common mistakes.
Loading…
ReadMeFeed / Community knowledge
#deno
Real questions. Useful conversations. Find the people who know your stack.
Deno's Built-in TypeScript: What Happens When You Skip the Build Step
Deno runs TypeScript directly by embedding the compiler and using snapshots for fast startup. The catch: execution skips type checking, so you need a separate `deno check` step.
Netlify Edge Functions: Geo‑Based Auth at the Edge
Add JWT authentication and country‑based redirects with Netlify Edge Functions. Learn Deno limits, setup steps, and how to verify the result in 900 words.
netlifyBehavior 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
Deno remote module cache vs CI pipeline: forcing revalidation of unversioned HTTPS imports without --reload wiping everything
Integration boundary A Deno service imports a handful of remote modules over plain HTTPS URLs (not a versioned registry like deno.land/x with @ tags). Locally and in CI, Deno caches these downloads under DENO_DIR keyed by URL, so once a URL is fetched it is not requested again on later runs. The upstream occasionally publishes fixes at the same URL, and the