Skip to content

Incorrect use of --directory param聽#19496

Description

@DenysVuika

馃悶 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

Activity

  1. modified the milestone: Backlog on Nov 30, 2020
  2. m-thompson-code commented on Apr 25, 2023

    @m-thompson-code

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions