Deno and Fresh introduce distinctive concepts — URL imports, explicit permissions, and islands architecture — that have their own vocabulary for technical discussions.
0 / 5 completed
1 / 5
A developer says: 'In Deno, you don't need npm — you import directly from a URL.' What does this mean?
Deno uses URL-based imports for its module system: import { serve } from 'https://deno.land/std/http/server.ts'. There's no node_modules folder or package.json by default. Modules are downloaded and cached globally on first use. This is a fundamental architectural difference from Node.js. Deno 2 added npm: specifiers for Node.js compatibility, but URL imports remain the idiomatic Deno approach.
2 / 5
In a Deno project discussion: 'Enable the permission flag for file access.' What is Deno's permission model?
Deno has a security-first permission model. By default, Deno scripts have no access to the file system, network, or environment variables. You grant permissions explicitly: --allow-read, --allow-net=api.example.com. This is a key selling point in security discussions — 'the script only has the permissions you grant it.' In code reviews, 'add the permission flag' means explicitly allow the needed system access.
3 / 5
A developer says: 'Fresh uses islands architecture for interactivity.' What does this mean?
Islands architecture means the page is mostly static HTML with small isolated interactive components ('islands') that get hydrated with JavaScript. Everything outside an island ships zero client-side JS. Fresh (Deno's web framework) uses this pattern — only files in the islands/ directory send JavaScript to the browser. In performance discussions: 'we're using islands' means minimal JavaScript, better performance.
4 / 5
A Deno developer says: 'Use deno.json to configure the project.' What is deno.json?
deno.json is Deno's project configuration file (similar to package.json for Node.js). It defines: import maps (aliases for URLs), task scripts (deno task dev), TypeScript compiler options, linting and formatting rules. When someone says 'configure it in deno.json,' they mean centralise project settings there rather than using CLI flags or separate config files.
5 / 5
An architect says: 'We chose Deno Deploy for edge deployment.' What is edge deployment?
Edge deployment means your code runs in globally distributed data centres close to users, rather than in a single region. Deno Deploy runs your code on Deno's edge network. This reduces latency because requests are handled by a server geographically close to the user. In architecture discussions: 'deploy to the edge' is about trading lower latency for constraints like no persistent file system or longer compute time.