bastianplsfix

← dev

Deno

Installing the runtime, the tools every example on this site is written with, and the longer walkthroughs of what Deno ships.

11 of 11 entries published. Published entries are linked; the rest are planned.

Prerequisites

Start here: install the tools, create the project, and wire the editor to Deno.

  1. Install Deno and check that it works

    One command installs the runtime that reads, checks, and runs every file here, and then you ask the tool itself to confirm it.

  2. Install Zed

    Deno runs programs; you still need somewhere to write them, and this editor is unusually good at showing what TypeScript is thinking.

  3. Create the course project

    One workspace, set up properly once, so a program you wrote weeks ago is still where you left it.

  4. Configure this Zed project to use Deno

    An editor understands your code by consulting a language server, and this project needs Deno's rather than the general-purpose one.

  5. Run and watch the current file from the editor

    Optional: a task and a keystroke that run the file you are editing, with the typed command still the ground truth.

Understanding Deno

The runtime's own surface: how a program prints, how a claim becomes a check, and where files and stored values live.

  1. The console

    A program prints on two streams, the console renders values for human eyes, and what it shows is a view of a value rather than the value itself.

  2. Assertions

    An assertion turns an expected result into a check that stays silent while it holds and throws when it breaks, and choosing an equality function means choosing what same means.

  3. Understanding testing

    A test turns one claim about a program into evidence you can check after every change, and Deno supplies the runner that grows those claims into a trustworthy suite.

  4. Understanding the file system

    Files hold bytes, directories hold names, and paths tell an operation where to look; every filesystem API builds on those three pieces.

  5. Deno KV

    The runtime's built-in database stores structured values under array keys, keeps every entry in key order, and lets several writes land together or not at all.

Guides

Longer-form walkthroughs that explain a topic before touching code, as a companion to the test-driven references.

  1. A guide to Deno KV

    What a key-value store is, how to use the API, and how the key space turns key design into the query language.