A Build & Deployment process for performance improvement of UI
How often do you struggle with caching issue of your JS code in browser during development & production? Do you somehow force hard reload of your JS app after releasing new version to production? What if you are releasing an update to only a small portion within a single page of your app/site? We’ll see how we can make the best use of caching in browser to achieve high performance of your web pages while still avoiding the risk of your users being served stale/old pages even after you release an update.
This talk is intended for audience familiar with React and RequireJS, although these are not a prerequisite.
In this session we’ll cover how to use a Grunt plugin’s hashing algorithm for versioning your files based on its contents.
How do you map original files to the new versioned files in Require.
Finally, we’ll see how to combine the power of composability of React components and the first two techniques above to achieve a highly efficient build process and a high performing web app.
I’m a frontend developer with extensive experience in building complex web apps from scratch involving several key architectural decisions, and also leading UI teams. I’ve been using React for about 2 years now. I also have given beginner to advanced level trainings in React to my teams.