I'm migrating a fully functional Angular SPA into AEM 6.5. Only a few pages will need authoring but the rest of the application will not need it. The application uses lazy loading and static routing. I'm aware of the Dynamic Routing rule of SPA Architecture. And I'm including dynamic routing for AEM only pages following: Getting Started with Angular and AEM SPA Editor - Chapter 2.
Currently, for non AEM pages with static routes, I see errors for x.model.json not being found. This makes sense since page "x" is not in AEM.
What is the best way to manage routing between non AEM pages with static routes and Angular/AEM pages? Is it possible to prevent the model service from looking for models in non AEM pages?
Adding reference to the SPA Design Model we are using.
@claudiab1560191 could you please create a ticket via  as, from my current understanding, this feature is meant to support your use-case. This will give us the time to investigate the issue more thoroughly.