Deno Rules
Secure JavaScript and TypeScript runtime. Run, test, lint, and bundle code with built-in tooling and permissions.
3 rules
deno.json Configuration Standards
Beginner
Every Deno project must use deno.json or deno.jsonc for centralized configuration — compiler options, import maps, tasks, lint and format settings, and permission declarations.
globs: **/deno.json, **/deno.jsonc, **/*.ts, **/*.tsx
deno-config, import-maps, tasks, jsr
View Rule
Explicit Permission Declarations
Intermediate
Always declare minimum required permissions explicitly — never use --allow-all in production, scope permissions to specific paths and hosts, and document why each permission is needed.
globs: **/deno.json, **/deno.jsonc, **/*.ts
permissions, security, sandbox, least-privilege
View Rule
Prefer Standard Library Over Third-Party
Beginner
Always prefer Deno's standard library (@std) over third-party packages for common tasks — file I/O, path manipulation, HTTP, testing, and data formats are all covered by the vetted std library.
globs: **/*.ts, **/*.tsx, **/deno.json, **/deno.jsonc
standard-library, jsr, dependencies, deno-std
View Rule