[Feature Request] Minimal Initial JavaScript Bundle for Authentication Redirect in OHIF Viewer

[sedghi]

What feature or change would you like to see made?

The OHIF Viewer currently initializes a large portion of its codebase, including extensions, modes, and services, before determining if user authentication is required. This results in a heavy initial JavaScript bundle and a slow initial load, even though the only immediate need is to redirect the user to the authentication provider. We propose creating a minimal initial JavaScript bundle that only includes the authentication service and a route handler for redirection. All other services, extensions, and modes should be lazily loaded after successful authentication, significantly improving initial load time, reducing bandwidth consumption, and providing a much snappier user experience. This requires refactoring the application's initialization logic and build process to implement code splitting and a two-phase loading approach.

Why should we prioritize this feature?

d

[sen-trenser]

@sedghi @IbrahimCSAE Could you please also consider an ability for extensions to provide a minimal js file to do any other document onload functionalities? This could be used for any consumer environment initialization/integration like logging, caching etc. services, custom configuration fetching, authentication etc. that needs to be done before OHIF app init..

Can webpack configured to bundle any onload.js script files from extension's public folder (when provided) and inject it in the platform app's index.html during build/publish?