Feedback: /runtime/desktop/configuration/ - Needs Improvement

[denobot]

Documentation Feedback

Path: /runtime/desktop/configuration/
Helpful: No ❌

Feedback:

Very excited to try out this new capability!

The deno desktop docs say:

Use --icon to set the application icon (.ico on Windows, .icns or .png on macOS), and --include / --exclude to add or remove files from the compiled binary. These can also be configured in deno.json; see Configuration.

However, this page doesn't mention anything about configuring --include via deno.json. It says this about specific frameworks:

For framework projects this is handled automatically: detected build outputs (.next/, dist/, _fresh/, .output/, etc.) are embedded in the binary's virtual filesystem and self-extracted at runtime so framework code finds them relative to its own working directory.

...but nothing about what I should do if I'm not using one of the supported frameworks.

GitHub User: @hunterloftis

---

This issue was automatically created from the documentation feedback system.