denoland / denoland/docs

Clarify Deno Desktop serving docs around loopback reachability

Open
#3,334 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
204
Forks
385
Avg merge
14h 49m
Merged PRs (30d)
7

Description

The Deno Desktop serving docs say the server is always bound to loopback, even if `0.0.0.0` is passed to `Deno.serve()`:

https://docs.deno.com/runtime/desktop/serving/

That explains why it is not reachable from other machines, but the page also says other apps and other users on the same machine cannot reach it. That part seems stronger than loopback binding alone guarantees.

Could the docs clarify whether Deno Desktop only forces loopback binding, or whether there is additional local-process isolation involved?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the Deno Desktop serving documentation at the linked page and compare its loopback-binding statement with its claim about access by other local apps and users. Verify whether Desktop adds process isolation beyond binding behavior. Done when the page accurately distinguishes remote reachability from same-machine reachability and explains the relevant limitation.

Written by the indexing model from the issue text.

Assessment

Tech stack
deno
Domain
documentation, networking
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.