GeezerVison is showing github.com — Incorrect use of --directory param · Issue #19496 · angular/angular-cli
Incorrect use of --directory param #19496
Description
🐞 Bug report
Command (mark with an x)
- new
- build
- serve
- test
- e2e
- generate
- add
- update
- lint
- extract-i18n
- run
- config
- help
- version
- doc
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
Reacted by Lukas Bischofberger and Mark Thompson
Activity
m-thompson-code commented on Apr 25, 2023
Is there a workaround for this? I want to be able to create angular applications based on an absolute path so I can create them in some temporary directory.
Metadata
Metadata
Development
No branches or pull requestsIssue actions