new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Deno · Reference · all subjects

cli commands/desktop

14 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

deno desktop --inspect flags

The --inspect, --inspect-wait, and --inspect-brk flags attach a debugger to both the Deno runtime and the renderer. The --inspect-renderer flag overrides the CEF renderer's debugger listen address.

deno desktop --hmr flag

The --hmr flag runs the app with hot module replacement during development. Usage: deno desktop --hmr main.ts

deno desktop command availability

The deno desktop command is available starting in Deno v2.9.0. If you are on an earlier version, you must update Deno to use it.

deno desktop basic purpose

The deno desktop command compiles a Deno project into a self-contained desktop application. The output binary bundles your code, the Deno runtime, and a rendering backend into one redistributable executable per platform.

deno desktop command examples

Example usage: deno desktop main.ts, deno desktop --hmr main.ts, deno desktop --output MyApp.app main.ts

deno desktop optional entrypoint

The entrypoint is optional. A bare deno desktop (or deno desktop .) detects a supported framework (Next.js, Astro, Fresh, React Router, and others) in the current directory and builds the appropriate desktop entrypoint.

deno desktop runtime flags

The deno desktop command accepts the same runtime and permission flags as deno run. The permissions you grant at compile time are baked into the compiled binary. For example: deno desktop --allow-read --allow-net main.ts

deno desktop --backend flag

The --backend flag selects the rendering engine. It accepts webview (the default) or cef. The raw backend is selected through the desktop.backend field in deno.json. Usage: deno desktop --backend webview main.ts

deno desktop --output flag

The --output (or -o) flag sets the output path; its extension determines the format (.app, .dmg, .AppImage, and so on). Usage: deno desktop --output ./dist/MyApp.dmg main.ts

deno desktop --icon flag

The --icon flag sets the application icon (.ico on Windows, .icns or .png on macOS). This can also be configured in deno.json.

deno desktop --include and --exclude flags

The --include and --exclude flags add or remove files from the compiled binary. These can also be configured in deno.json.

deno desktop --target flag

The --target flag builds for another platform. No platform-specific toolchain is needed on the host. Usage: deno desktop --target aarch64-apple-darwin main.ts

deno desktop --all-targets flag

The --all-targets flag builds for every supported platform at once. No platform-specific toolchain is needed on the host. Usage: deno desktop --all-targets main.ts

deno desktop command

deno desktop is used to build a desktop app from the current Deno project.

Give your agent this brain