You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there an existing issue that is already proposing this?
I have searched the existing issues
Is your feature request related to a problem? Please describe it
I am following the workspace guide and was a bit surprised that in order to initiate a monorepo mode you must start with standard mode as a first step. On my opinion this is a bit confusing approach.
To enable monorepo mode, you start with a standard mode structure... (c)
Describe the solution you'd like
I would like to be able to start a new workspace project with an empty workspace
What is the motivation / use case for changing the behavior?
I would like propose a feature similar to angular empty workspace. I find this approach more reasonable and looking forward for your thoughts.
If you plan to have multiple applications in the workspace, you can create an empty workspace by using the --no-create-application option. You can then use ng generate application to create an initial application. This allows a workspace name different from the initial app name, and ensures that all applications reside in the /projects subfolder, matching the structure of the configuration file. (c) as per https://angular.dev/cli/new
The text was updated successfully, but these errors were encountered:
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
I am following the workspace guide and was a bit surprised that in order to initiate a monorepo mode you must start with standard mode as a first step. On my opinion this is a bit confusing approach.
To enable monorepo mode, you start with a standard mode structure... (c)
Describe the solution you'd like
I would like to be able to start a new workspace project with an empty workspace
Teachability, documentation, adoption, migration strategy
What is the motivation / use case for changing the behavior?
I would like propose a feature similar to angular empty workspace. I find this approach more reasonable and looking forward for your thoughts.
If you plan to have multiple applications in the workspace, you can create an empty workspace by using the --no-create-application option. You can then use ng generate application to create an initial application. This allows a workspace name different from the initial app name, and ensures that all applications reside in the /projects subfolder, matching the structure of the configuration file. (c) as per https://angular.dev/cli/new
The text was updated successfully, but these errors were encountered: