Feedback: /runtime/desktop/configuration/ - Needs Improvement
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- documentation
Research direction
Open the /runtime/desktop/configuration/ page and compare its --include and deno.json descriptions with the linked Configuration guidance. Clarify how non-framework projects configure files for inclusion, including the deno.json form, and ensure the page explains what users should do when automatic framework detection does not apply.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- TypeScript
- Stars
- 205
- Forks
- 386
- Avg merge
- 5d 19h
- Merged PRs (30d)
- 4
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from denoland/docs
-
feedback needs-improvement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
feedback needs-improvement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
feedback needs-improvement
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
feedback needs-improvement
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
feedback needs-improvement
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100