Hi Jose, Routes need to be available during compile time. This has to do with the fact, that if a route is not in the router, the tree-shaker will shake it away. If that happens, the code you are trying to load is not in your application. I assume you see the issue there.
If you need to be able to dynamically add routes, that is possible, but you have to make sure the things you add to your router are in the actual production version of your app. (check out the router.resetConfig <https://angular.io/api/router/Router#resetConfig>) Regards Sander -- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
