Allow running `deno init -A` to support CI or non-prompt supporting envs

[csvn]

Currently, the available options for deno init (deno init --help) are:

scaffolds a basic Deno project with a script, test, and configuration file

Usage: deno init [OPTIONS] [DIRECTORY OR PACKAGE]...

Arguments:
  [DIRECTORY OR PACKAGE]...

Options:
  -h, --help[=<CONTEXT>]  [possible values: unstable, full]
      --lib               Generate an example library project
      --npm               Generate a npm create-* project
  -q, --quiet             Suppress diagnostic output
      --serve             Generate an example project for `deno serve`

This means there's no way to run run this command e.g. in CI to scaffold a project, because there's no -A/-y or --force flags to pre-approve the command. The command will just fail with "Permission denied (os error 13)".

Solution

Add -A/--allow-all as a flag to deno init?

Rererences

• PR: feat(@angular/cli): allow using Deno as package manager angular/angular-cli#30948
• https://github.com/csvn/angular-cli/blob/aa6cb3f3f5da5113aece90b6dca298dba4c24c1a/tests/legacy-cli/e2e/tests/misc/create-angular.ts#L30
• Workflow error: https://github.com/angular/angular-cli/actions/runs/19930308000/job/57140846701?pr=30948#step:6:2928

[dsherret]

I think we should just add a --yes flag here, though maybe -A would make sense too (edit: actually -A probably wouldn't be good because it would give the false impression that running without it would be no permissions).

The command will just fail with "Permission denied (os error 13)".

It's supposed to exit with something like:

You can initialize project manually by running deno run npm:@angular/create` and applying desired permissions.

[csvn]

It's supposed to exit with something like:

You're right. I wanted to verify this, and I get the below when I run the command in GitHub Actions directly.

The error I linked may be another issue, I'll try to find the cause of that outside this issue 😅

error: Can't set up 'ng' bin at /tmp/angular-cli-e2e-YXwFfm/e2e-test/test-project/node_modules/.deno/@angular+cli@21.1.0-next.1/node_modules/@angular/cli/bin/ng.js

I think we should just add a --yes flag here, though maybe -A would make sense too (edit: actually -A probably wouldn't be good because it would give the false impression that running without it would be no permissions).

Is it not true that there's no permissions by default currently? Passing y to the prompt seems to be pretty similar to using -A to allow everything? Though using --yes seems to be pretty similar to apt --yes to just approve prompts, so that makes sense too. 🙂

As long as the flag is clearly indicating to pre-approve prompts, I think that's a good choice. 👍