Abstract: A system can improve application performance by using lazy loading of code containers based on non-navigational actions in single-page or hybrid applications. A page can launch by loading a main bundle of code. The main bundle can include an action manifest that maps action identifiers to separate code modules. Those separate code modules can include functions for handling the actions. Based on a non-navigational action that occurs, the application can use the action manifest to map a first action identifier of the first action to a first code module. The application can then lazy load a first code module asynchronously from the main bundle. The application can also use route guards with filters to determine child actions, validate action routes, and cache the validated routes for later use without a remote server call.

Abstract: A system can improve application performance by using lazy loading of code containers based on non-navigational actions in single-page or hybrid applications. A page can launch by loading a main bundle of code. The main bundle can include an action manifest that maps action identifiers to separate code modules. Those separate code modules can include functions for handling the actions. Based on a non-navigational action that occurs, the application can use the action manifest to map a first action identifier of the first action to a first code module. The application can then lazy load a first code module asynchronously from the main bundle. The application can also use route guards with filters to determine child actions, validate action routes, and cache the validated routes for later use without a remote server call.