Vishakha Tak well, in my case i know the base path my app will be deployed behind, so i pretty much went with this but with /whatever instead of a relative link like ./

Thanks for the info. This seems like it wont work if you have routes that are loaded directly though? e.g. if a user clicks a link to your app like site.com/some-base-path/some/route/in/the/app The browser is going to try load runtime.js etc from site.com/some-base-path/some/route/in/the/runtime.js Whereas it actually sits at site.com/some-base-path/runtime.js Any suggestions how to tackle that?