Skip to content

docs: clarify that Deno runtime flags can't be passed on Deploy#3310

Merged
bartlomieju merged 1 commit into
mainfrom
docs/deploy-runtime-args-note
Jun 18, 2026
Merged

docs: clarify that Deno runtime flags can't be passed on Deploy#3310
bartlomieju merged 1 commit into
mainfrom
docs/deploy-runtime-args-note

Conversation

@bartlomieju

Copy link
Copy Markdown
Member

Feedback on the builds reference asked how to pass Deno runtime arguments such
as --unstable-* on Deno Deploy, and couldn't find an answer.

The answer already lives in the runtime reference ("the runtime runs with
--allow-all" and "custom flags cannot be passed to the Deno runtime"), but it
wasn't surfaced on the builds page, where the "Arguments" / deploy.runtime.args
option is described only as "command-line arguments to pass to the application".
That wording reads as if it might cover runtime flags, when in fact those
arguments go to the application after the entrypoint.

This clarifies both the dashboard "Arguments" option and the deploy.runtime.args
source-code option to say the arguments are passed to the application after the
entrypoint and are not Deno runtime flags, with a link to the runtime reference.
It also names --unstable-* explicitly in the runtime reference so the term is
searchable from where users look.

Closes #2398.

@bartlomieju
bartlomieju merged commit e41d830 into main Jun 18, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Feedback: /deploy/early-access/reference/builds/ - Needs Improvement

1 participant