馃悶 Bug report
Command (mark with an x)
Is this a regression?
No, this issue has been in the CLI for a long time
Description
When using the --directory param with the absolute path, the CLI does not respect the value and creates the directory path relative to the current directory instead.
馃敩 Minimal Reproduction
Run the following command:
ng new app1 --directory=/tmp/app1 --skip-install
Expected behaviour:
The application is generated within /tmp/app1 directory.
Actual behaviour:
The application is generated within current directory: ./tmp/app1
馃實 Your Environment
Angular CLI: 11.0.2
Node: 14.15.0
OS: darwin x64
Angular:
...
Ivy Workspace:
Package Version
------------------------------------------------------
@angular-devkit/architect 0.1100.2 (cli-only)
@angular-devkit/core 11.0.2 (cli-only)
@angular-devkit/schematics 11.0.2 (cli-only)
@schematics/angular 11.0.2 (cli-only)
@schematics/update 0.1100.2 (cli-only)
Anything else relevant?
Using macOS
馃悶 Bug report
Command (mark with an
x)Is this a regression?
No, this issue has been in the CLI for a long time
Description
When using the
--directoryparam with the absolute path, the CLI does not respect the value and creates the directory path relative to the current directory instead.馃敩 Minimal Reproduction
Run the following command:
Expected behaviour:
The application is generated within
/tmp/app1directory.Actual behaviour:
The application is generated within current directory:
./tmp/app1馃實 Your Environment
Anything else relevant?
Using macOS