-
Notifications
You must be signed in to change notification settings - Fork 12k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
-dir
flag not being respected
#5867
Comments
I was unable to reproduce this using
Using
|
My apologies, I debugged it more and found that the issue required more specific conditions to dupe and forgot to update this bug report. This is specifically if a directory above contains a In other words, my expected setup was ng new -dir packages/foo-app foo resulting in
but instead I got
|
I actually thought we fixed this already in #4901. Maybe something is broken. |
This has been fixed a long time ago, never marked. If this still happens please create a new issue so we can follow up. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Bug Report or Feature Request (mark with an
x
)Versions.
@angular/cli: 1.0.0
node: 7.7.1
os: win32 x64 (Windows 10 1703 Build 15063.14 "Creators Update" RC)
@angular/common: 4.0.1
@angular/compiler: 4.0.1
@angular/core: 4.0.1
@angular/flex-layout: 2.0.0-beta.7
@angular/http: 4.0.1
@angular/material: 2.0.0-beta.2
@angular/platform-browser: 4.0.1
@angular/platform-browser-dynamic: 4.0.1
Repro steps.
ng new -dir foo myapp
./foo
The log given by the failure.
Correct output for app generation
Desired functionality.
The app should be created in
./foo
, as indicated in the help text:Mention any other details that might be useful.
The text was updated successfully, but these errors were encountered: