Are you experiencing any errors when running ng new? As I am unable to replicate this issue.

@alan-agius4, no the problem is not with ng new. Sorry for the misunderstanding. Basically, my observation is related to ng g app command.

When a workspace with --create-application false flag is created, the initial application in src folder is not being generated, nor the related dependencies added to package.json.

Generating an app right after that will result with the app in the projects and with the new dev dependency @angular-devkit/build-angular added to package.json.

That's all fine, however, since package manager was not triggered @angular-devkit/build-angular is not installed yet, so executing ng serve now will result in an error.

I was thinking that a package manager has to be triggered after the app generation the same way as it is when generating a library (as well --skip-install flag is available in the library schematic).

Thanks, for the explanation. I now see the problem.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}