-
Notifications
You must be signed in to change notification settings - Fork 12k
listLazyRoutes is now undefined did something change #3714
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
Comments
Good thing I'm not the only one. Just created a new project with "ng new [project_name]" and tried "ng build" immediately. Gave me the error on a completely new project. I saw that it got changed in commit bd03100 |
@hansl angular/angular@7256d0e (the change that added support to 2.3.1, 2.4.0-marker, 2.4.0, 2.4.1 all those versions lack the needed commit (Commits on Dec 13, 2016) I looked into the https://github.com/angular/angular/releases I could be wrong if those are not in sync with npm's releases. |
Seems to be fixed now. |
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. |
OS?
Versions.
Repro steps.
The log given by the failure.
Mention any other details that might be useful.
The text was updated successfully, but these errors were encountered: