Skip to content

fix(@ngtools/webpack): if the router is not found ignore lazy routes #6980

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

Merged
merged 1 commit into from
Jul 14, 2017

Conversation

hansl
Copy link
Contributor

@hansl hansl commented Jul 14, 2017

Fixes #5967

If the router isnt in node_modules then there's no reason to fail, just pretend there are no lazy routes.

Fixes angular#5967

If the router isnt in node_modules then there's no reason to fail, just pretend there are no lazy routes.
@hansl hansl merged commit 962b028 into angular:master Jul 14, 2017
@hansl hansl deleted the no-angular-router branch July 14, 2017 19:00
@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 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ng build should not require @angular/* modules that are not used
3 participants