-
Notifications
You must be signed in to change notification settings - Fork 12k
Angular CLI 6.0.0-rc.4 can't run ng build
on Windows
#10328
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
Labels
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Milestone
Comments
doggy8088
added a commit
to doggy8088/devkit
that referenced
this issue
Apr 13, 2018
The drive letter could be lower case. This PR fix angular/angular-cli#10328
@hansl bug fixed. please check for angular/devkit#697 |
doggy8088
added a commit
to doggy8088/devkit
that referenced
this issue
Apr 13, 2018
The Windows drive letter could be lower case. This PR fix angular/angular-cli#10328
doggy8088
added a commit
to doggy8088/devkit
that referenced
this issue
Apr 14, 2018
The Windows drive letter could be lower case. This PR fix angular/angular-cli#10328
hansl
pushed a commit
to angular/devkit
that referenced
this issue
Apr 15, 2018
The Windows drive letter could be lower case. This PR fix angular/angular-cli#10328
hansl
pushed a commit
that referenced
this issue
Jun 6, 2018
The Windows drive letter could be lower case. This PR fix #10328
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Versions
Repro steps
npx @angular/cli@next new ng6app
cd ng6app
ng build
Observed behavior
When I run
ng build
in Command Prompt, it failed.**When I open this folder and open Terminal to run the same command, it works! **
Desired behavior
It suppose can run these command both in Command Prompt and in Terminal of VSCode.
Mention any other details that might be useful (optional)
I tried to output the problem path. In Command Prompt, the path start with 'G:/'. In Terminal window of the VSCode, it do start with '/'. (Why?)
The text was updated successfully, but these errors were encountered: