ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Context Ionic 7+ applications using the default Vite builder load environment variables from .env files during both ionic serve and ionic build --prod . Vite's documented behavior requires a VITE_ prefix for variables to be exposed to the client bundle via import.meta.env . Observed discrepancy During development with ionic serve , Vite's dev server injects
I have an Ionic app that needs to authenticate in Azure, so I installed MSAL following this tutorial: https://learn.microsoft.com/en-us/graph/tutorials/angular It works like a charm with "ionic serve" but when I run it in the device, it crashes when I try to sign in Azure. I think it is because the popup window MSAL shows for login is not allowed in Ionic. S
Lifecycle mismatch between Angular and Ionic navigation Ionic's IonRouterOutlet caches component instances in the DOM to preserve scroll position and state across forward navigation. This caching behavior means Angular's ngOnDestroy hook does not fire when navigating away from a page via routerLink or NavController.push . Instead, the component remains attac
Developers configuring a custom proxy in Ionic 6 projects often encounter inconsistent livereload behavior when the proxy object includes host and port fields. The built-in livereload server defaults to port 35729, and redirecting this endpoint can prevent the client from establishing a connection, resulting in stale UI updates that require manual page refre
angular
ionic
vite