๐ช๐๐๐ก ๐ ๐ฆ๐๐ ๐ฃ๐๐ ๐ฅ๐๐๐ฅ๐๐ฆ๐ ๐๐ฅ๐ข๐๐ ๐ข๐จ๐ฅ ๐๐ฃ๐ฃ
We found a bug. Top routes worked fine. Deep routes caused full page reloads. The sidebar reset every time. The app felt unstable.
It worked locally. It failed in production.
We used Next.js static export on Azure Static Web Apps. This setup has no server runtime. It serves static files.
The issue was soft navigation. Next.js needs route payload data for smooth transitions. It needs HTML for the first load.
Our Azure rewrite rules were too broad. Azure sent HTML when Next.js asked for payload data. The router failed. The app reloaded.
We fixed this with automation. We built a tool to generate rewrite rules from build output. The tool now:
- Scans for dynamic route files.
- Creates specific rules for HTML and payloads.
- Orders rules by priority.
- Writes the final config file.
This removed manual errors.
If you use static export on Azure:
- Automate your config files.
- Test soft navigation.
- Check if payload requests return HTML.
- Treat rewrite rules as critical infrastructure.
Hard frontend bugs often live between build output and hosting rules.