docs: cli-reference for `ng new` incorrectly shows --standalone as defaulting to false

[mvdluit]

Describe the problem that you experienced

The cli reference (adev) for the the new command lists the --standalone flag, mentioning it defaults to false. In v17 standalone is the default behavior. Note that on https://angular.io/cli/new the --standalone flag correctly says that it defaults to true.

The --no-standalone flag is missing (also on angular.io) and IMO could be listed in place of the --standalone flag since that is default behavior now.

Enter the URL of the topic with the problem

https://angular.dev/cli/new

Describe what you were looking for in the documentation

No response

Describe the actions that led you to experience the problem

No response

Describe what you want to experience that would fix the problem

• Update the --standalone flag to correctly show it's the default behavior (e.g default true). (or maybe replace it with the --no-standalone as it's now the default behavior.)

• Add --no-standalone flag to inform how to create a project based on NgModules. (both on .dev and .io).

Add a screenshot if that helps illustrate the problem

No response

If this problem caused an exception or error, please paste it here

No response

If the problem is browser-specific, please specify the device, OS, browser, and version

No response

Provide any additional information here in as much as detail as you can

No response

[alan-agius4]

For context: --no is available to all boolean options. As described in https://angular.io/cli#boolean-options

[mvdluit]

@alan-agius4 Thank you for pointing that out. This explanation about --no being available on boolean values does not seem to be present on angular.dev. In fact, the entire overview page on adev is missing the explanation on the basics of the CLI. Should I make a separate issue for this?

Some context as to why I would like to see an explicit mention of --no-standalone: Since standalone became the default, people asking about missing modules is a daily recurring event on the Angular Discord. A lot of people starting out with Angular are still following NgModule based courses/guides, and it's hard for them to discover how to generate a project with modules. Having at least the CLI reference explicitly mention the possibility of generating a NgModule project would therefore be helpful in my opinion.

I (and other people involved with the discord) fully support standalone being the default and are trying to get people to try it out, but it will probably take some time for courses/guides to catch up. (When Angular turned on TS strict by default, it also took nearly 2 major versions for the questions about it to become less 😬)

[JeanMeche]

I don't think we should recommend people to go with --no-standalone and not mentionning it would be the right direction to do so.

With the time we'll see more and more content that will drop the ngModules.

[mvdluit]

@JeanMeche I agree that a specific mention of --no-standalone is not necessary (we solved it with a /standalone bot command on discord so we don't have to spend too much time on these questions).

A lot of the information from the overview page for the CLI is still missing though: https://angular.io/cli
ADEV only shows commands and some basic explanation could be useful.

[CarlosLiberJesus]

Just looking for answers too... just booted the WSL to start work, did a normal ng g c ... and the standalone: true started to appear as the warning message! Even in older projects that I wasn't toutch, addind in ~.angular.config.json did not work...

The best I could so far, was in project forder angular.json:
"@schematics/angular:component": {
"style": "scss",
"standalone": false
},

that managed to create well the components, but the warning message does not go away and my autism doesnt like it