Can Deno "compile" bundle a full webapp into a single file?

From what I can tell, neither Deno nor Oak have intentional support for this.

A downside of even doing this is that your binary file may become large. This isn't only an issue with distribution but may also slow loading and executing the binary.

Nevertheless, one way you can make "static" files available in a compiled binary is to encode the files as JavaScript modules (similar to using WebAssembly in Deno).

e.g. The following module encodes a static file, named example.txt, storing its file type, txt, and its contents, hello world\n. The contents are base64 encoded (thank you jsejcksn for the suggestion). You can encode and decode the contents other ways as well or even use different encodings depending on the file type if you like.

example.txt.ts:

export default {
  type: "txt",
  data: "aGVsbG8gd29ybGQK",
};

You can programmatically create modules like this from static files.

e.g. encode-as-module.ts:

import { extname } from "https://deno.land/std@0.155.0/path/mod.ts";
import { encode } from "https://deno.land/std@0.155.0/encoding/base64.ts";

const [inputPath, outputPath = `${inputPath}.ts`] = Deno.args;
const type = extname(inputPath).slice(1);
const bytes = await Deno.readFile(inputPath);

const script = /* JavaScript */ `export default {
  type: "${type}",
  data: "${encode(bytes)}",
};
`;

await Deno.writeTextFile(outputPath, script);

Usage:

deno run --allow-read --allow-write encode-as-module.ts example.txt

Once you have your static files encoded as modules you can then change your Oak app from serving them using send() to serving them using context.response (passing the type and body). More work will need to be done here to encode a list of all the static files, etc. but I think what's already provided here illustrates the idea sufficiently.