Skip to content

Tracking: replace --ng4 flag with --ng2 flag on ng new #5566

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.

Sign up for GitHub

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

Jump to bottom
Closed
filipesilva opened this issue Mar 22, 2017 · 1 comment · Fixed by #5575
Closed

Tracking: replace --ng4 flag with --ng2 flag on ng new #5566

filipesilva opened this issue Mar 22, 2017 · 1 comment · Fixed by #5575
Labels
P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful

Comments

@filipesilva
Copy link
Contributor

filipesilva commented Mar 22, 2017 •
edited
Loading

For 1.0 final, ng new should generate an Angular version 4 project.

Our e2e test setup on travis also needs to take this into account.
@filipesilva filipesilva added the P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful label Mar 22, 2017
@filipesilva filipesilva added this to the 1.0 Final Blocking milestone Mar 22, 2017
filipesilva added a commit to filipesilva/angular-cli that referenced this issue Mar 22, 2017
@filipesilva
feat(@angular/cli): always use ng4 in ng new
fd1741c 
Fix angular#5566
@filipesilva filipesilva mentioned this issue Mar 22, 2017
Merged
filipesilva added a commit to filipesilva/angular-cli that referenced this issue Mar 23, 2017
@filipesilva
feat(@angular/cli): always use ng4 in ng new
7aec599 
Fix angular#5566
filipesilva added a commit to filipesilva/angular-cli that referenced this issue Mar 24, 2017
@filipesilva
feat(@angular/cli): always use ng4 in ng new
830c53c 
Fix angular#5566
filipesilva added a commit to filipesilva/angular-cli that referenced this issue Mar 24, 2017
@filipesilva
feat(@angular/cli): always use ng4 in ng new
77a9f5f 
Fix angular#5566
filipesilva added a commit to filipesilva/angular-cli that referenced this issue Mar 24, 2017
@filipesilva
feat(@angular/cli): always use ng4 in ng new
9b26d13 
Fix angular#5566
hansl pushed a commit that referenced this issue Mar 24, 2017
@filipesilva @hansl
feat(@angular/cli): always use ng4 in ng new
baf0c7d 
Fix #5566
@bogacg bogacg mentioned this issue Mar 24, 2017
Closed
@nethulap nethulap mentioned this issue Apr 26, 2017
Closed
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(@angular/cli): always use ng4 in ng new filipesilva/angular-cli
2 participants
@hansl @filipesilva