docs: 2.8

api/web/index.md

@@ -72,6 +72,55 @@ Deno supports a comprehensive set of web standard APIs:
 - **[Timers](/api/web/~/setTimeout)** - setTimeout, setInterval, and
   setImmediate
 
+### Structured Clone & Transferable Objects
+
+Deno supports [`structuredClone()`](/api/web/~/structuredClone) and
+[`postMessage()`](/api/web/~/Worker) for cloning and transferring objects across
+contexts (e.g. between the main thread and Web Workers).
+
+#### Serializable types
+
+These types can be cloned with `structuredClone()` and sent via `postMessage()`:
+
+| Type                                      | Notes                                                                                        |
+| ----------------------------------------- | -------------------------------------------------------------------------------------------- |
+| Primitives                                | `string`, `number`, `boolean`, `null`, `undefined`, `bigint`                                 |
+| `Array`, `Object`, `Map`, `Set`           | Including nested structures and circular references                                          |
+| `Date`, `RegExp`                          |                                                                                              |
+| `ArrayBuffer`, `TypedArray`, `DataView`   | Copied by default, or transferred (see below)                                                |
+| `Error` types                             | `Error`, `EvalError`, `RangeError`, `ReferenceError`, `SyntaxError`, `TypeError`, `URIError` |
+| [`Blob`](/api/web/~/Blob)                 | Requires Deno 2.8+                                                                           |
+| [`File`](/api/web/~/File)                 | Requires Deno 2.8+                                                                           |
+| [`DOMException`](/api/web/~/DOMException) |                                                                                              |
+| [`CryptoKey`](/api/web/~/CryptoKey)       |                                                                                              |
+
+#### Transferable types
+
+These types can be _transferred_ (not copied) via the `transfer` option in
+`structuredClone()` or the `transfer` list in `postMessage()`. After transfer,
+the original object becomes unusable:
+
+| Type                                            | Notes                                    |
+| ----------------------------------------------- | ---------------------------------------- |
+| [`ArrayBuffer`](/api/web/~/ArrayBuffer)         | Moves the backing memory to the receiver |
+| [`MessagePort`](/api/web/~/MessagePort)         | Transfers the port to another context    |
+| [`ReadableStream`](/api/web/~/ReadableStream)   | Transfers the stream to another context  |
+| [`WritableStream`](/api/web/~/WritableStream)   | Transfers the stream to another context  |
+| [`TransformStream`](/api/web/~/TransformStream) | Transfers the stream to another context  |
+
+```ts
+// Clone a Blob
+const blob = new Blob(["hello"], { type: "text/plain" });
+const cloned = structuredClone(blob);
+console.log(await cloned.text()); // "hello"
+
+// Transfer an ArrayBuffer through a MessageChannel
+const buffer = new ArrayBuffer(1024);
+const ch = new MessageChannel();
+ch.port1.postMessage(buffer, [buffer]);
+// buffer.byteLength is now 0 (transferred)
+```
+
 ## Key Benefits
 
 - **Standards Compliance**: APIs follow WHATWG and W3C specifications

examples/scripts/importing_text.ts

@@ -2,14 +2,15 @@
  * @title Importing text files
  * @difficulty beginner
  * @tags cli
- * @run --unstable-raw-imports https://docs.deno.com/examples/scripts/importing_text.ts
+ * @run <url>
  * @resource {https://github.com/whatwg/html/issues/9444} HTML specification proposal
- * @group Unstable APIs
+ * @group Basics
  *
  * Text files can be imported in JS and TS files using the `import` keyword.
  * This makes including static data in a library much easier.
  *
- * Using this feature requires `--unstable-raw-imports` CLI flag.
+ * Stable as of Deno 2.8 — no flag required. (Binary `bytes` imports are still
+ * experimental and require `--unstable-raw-imports`.)
  */
 
 // File: ./main.ts

examples/tutorials/os_signals.md

@@ -1,5 +1,5 @@
 ---
-last_modified: 2025-03-10
+last_modified: 2026-05-20
 title: "Handle OS signals"
 description: "Tutorial on handling operating system signals in Deno. Learn how to capture SIGINT and SIGBREAK events, manage signal listeners, and implement graceful shutdown handlers in your applications."
 url: /examples/os_signals_tutorial/
@@ -8,7 +8,9 @@ oldUrl:
   - /runtime/tutorials/os_signals/
 ---
 
-> ⚠️ Windows only supports listening for SIGINT and SIGBREAK as of Deno v1.23.
+> ⚠️ Windows supports listening for `SIGINT`, `SIGBREAK`, `SIGTERM`, `SIGQUIT`,
+> `SIGHUP`, and `SIGWINCH` (all except `SIGINT`/`SIGBREAK` go through libuv's
+> Windows signal emulation).
 
 ## Concepts
 
@@ -75,3 +77,18 @@ Run with:
 ```shell
 deno run signal_listeners.ts
 ```
+
+## Windows support
+
+The supported signal set differs between platforms. The Windows-specific
+behavior is:
+
+| Use case                         | Supported signals on Windows                                                                                                       |
+| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
+| `Deno.addSignalListener(sig, …)` | `SIGINT`, `SIGBREAK`, `SIGTERM`, `SIGQUIT`, `SIGHUP`, `SIGWINCH`                                                                   |
+| `Deno.kill(pid, sig)`            | `SIGINT`, `SIGBREAK`, `SIGTERM`, `SIGQUIT`, `SIGHUP`, `SIGWINCH`, `SIGKILL`, `SIGABRT`, plus signal `0` for a process-health check |
+
+`SIGKILL` and `SIGABRT` are deliberately **not** registerable via
+`addSignalListener` — they're uncatchable / fatal, matching Unix semantics. On
+Windows the catchable signals all forward to libuv's emulation layer; signals
+sent via `Deno.kill` ultimately invoke `TerminateProcess`.

lint/rules/no-node-globals.md

@@ -1,5 +1,5 @@
 ---
-tags: [recommended]
+tags: []
 ---
 
 Disallows the use of NodeJS global objects.
@@ -8,6 +8,19 @@ NodeJS exposes a set of global objects that differs from deno (and the web), so
 code should not assume they are available. Instead, import the objects from
 their defining modules as needed.
 
+This rule is **off by default** as of Deno 2.8. To opt in, add it to your
+`deno.json`:
+
+```json
+{
+  "lint": {
+    "rules": {
+      "include": ["no-node-globals"]
+    }
+  }
+}
+```
+
 **Invalid:**
 
 ```typescript

lint/rules/no-process-global.md

@@ -1,5 +1,5 @@
 ---
-tags: [recommended]
+tags: []
 ---
 
 Disallows the use of NodeJS `process` global.
@@ -8,6 +8,19 @@ NodeJS and Deno expose `process` global but they are hard to statically analyze
 by tools, so code should not assume they are available. Instead,
 `import process from "node:process"`.
 
+This rule is **off by default** as of Deno 2.8. To opt in, add it to your
+`deno.json`:
+
+```json
+{
+  "lint": {
+    "rules": {
+      "include": ["no-process-global"]
+    }
+  }
+}
+```
+
 **Invalid:**
 
 ```typescript

runtime/_data.ts

@@ -116,6 +116,10 @@ export const sidebar = [
             title: "deno bench",
             href: "/runtime/reference/cli/bench/",
           },
+          {
+            title: "deno bump-version",
+            href: "/runtime/reference/cli/bump_version/",
+          },
           {
             title: "deno bundle",
             href: "/runtime/reference/cli/bundle/",
@@ -124,6 +128,10 @@ export const sidebar = [
             title: "deno check",
             href: "/runtime/reference/cli/check/",
           },
+          {
+            title: "deno ci",
+            href: "/runtime/reference/cli/ci/",
+          },
           {
             title: "deno clean",
             href: "/runtime/reference/cli/clean/",
@@ -184,6 +192,10 @@ export const sidebar = [
             title: "deno outdated",
             href: "/runtime/reference/cli/outdated/",
           },
+          {
+            title: "deno pack",
+            href: "/runtime/reference/cli/pack/",
+          },
           {
             title: "deno publish",
             href: "/runtime/reference/cli/publish/",
@@ -220,6 +232,10 @@ export const sidebar = [
             title: "deno test",
             href: "/runtime/reference/cli/test/",
           },
+          {
+            title: "deno transpile",
+            href: "/runtime/reference/cli/transpile/",
+          },
           {
             title: "deno types",
             href: "/runtime/reference/cli/types/",
@@ -240,6 +256,10 @@ export const sidebar = [
             title: "deno unstable flags",
             href: "/runtime/reference/cli/unstable_flags/",
           },
+          {
+            title: "deno why",
+            href: "/runtime/reference/cli/why/",
+          },
           {
             title: "deno x",
             href: "/runtime/reference/cli/x/",
@@ -330,6 +350,10 @@ export const sidebar = [
         title: "Lint plugins",
         href: "/runtime/reference/lint_plugins/",
       },
+      {
+        title: "Module customization hooks",
+        href: "/runtime/reference/module_hooks/",
+      },
       {
         title: "WebAssembly",
         href: "/runtime/reference/wasm/",

runtime/fundamentals/configuration.md

@@ -744,6 +744,27 @@ this requires an explicit opt-in with `-P` and is not loaded by default.
 
 If you're ok with this risk, then this feature will be useful for you.
 
+## Compile config
+
+The `"compile"` block configures
+[`deno compile`](/runtime/reference/cli/compile/) without requiring you to
+repeat flags on every invocation. You can declare which extra files or
+directories to bundle into the executable, and which paths to exclude:
+
+```jsonc title="deno.json"
+{
+  "compile": {
+    "include": ["names.csv", "data", "worker.ts"],
+    "exclude": ["data/secrets", "**/*.test.ts"]
+  }
+}
+```
+
+`--include` and `--exclude` flags on the command line are merged with these
+lists rather than replacing them. The `"compile"` block can also carry
+`permissions` (see
+[Test, bench, and compile permissions](#test-bench-and-compile-permissions)).
+
 ## An example `deno.json` file
 
 ```json