We went through steps to enable code splitting in Part 1. As mentioned in Part 1, it’s not working right at server-side rendering yet. What exactly the problem is? Exercise: see the problem with actual code You can skip this section if you already know the problem or don’t bother to run/test with actual code. You can see the problem…
-
-
React code splitting and server-side rendering with ASP.NET Core – Part 1
Thanks to [crayon-641821165a38e188574657-i/], code splitting has become easy with dynamic [crayon-641821165a393593790871-i/]. However, for code splitting to work together with server-side rendering, things become more tricky and not that straight forward because at the server side, the modules have to be loaded synchronously in order to render the page correctly. There are several different available loaders that can help get the…
-
Simple long polling in ASP.NET Core SPA
Typically, ASP.NET MVC model handles requests by receiving the request, do some processing and then return the response, all within an action method. But in case of doing a long polling, we don’t have anything to return until the expected event occurs. Therefore, the long polling request needs to be able to wait for the event, without holding up the…
-
redux-first-router, migrate from redux-little-router, for React/Redux SPA
This is a simple tutorial showing how to switch from [crayon-641821165cc05116481274-i/] to [crayon-641821165cc0a183001444-i/]. The settings are pretty similar so the changes should be easy to understand. For more information about comparison of the 2 router packages, check out my other post redux-first-router vs redux-little-router for React/Redux SPA Get started Goal: To use [crayon-641821165cc0b761659857-i/]. Base project code: Example code from React Routing with redux-little-router, ASP.NET…
-
redux-first-router vs redux-little-router for React/Redux SPA
Client side routing is definitely one of the center piece of gears that empowers single page application. For our [crayon-641821165d18b700923844-i/] projects, we have been using [crayon-641821165d18f732123286-i/] that fits in reasonably well. Recently, I had a chance to hand on evaluating and trying out another router package, [crayon-641821165d190792659339-i/]. Both packages are designed with [crayon-641821165d191524193515-i/] in mind and so they both work and integrate well with…
-
Improve React/Redux SPA Performance, with ASP.NET Core – Part 2
After taking steps to optimize React component rendering discussed in Improve React/Redux SPA Performance Part 1, let’s look at other aspect of the application that can further improve the performance and loading speed. Minimize application bundle size The smaller the application bundle size, the faster the initial loading would be. Code splitting The initial bundle only contains modules needed to render…
-
Improve React/Redux SPA Performance, with ASP.NET Core – Part 1
Fast web experience is what users expect nowadays. Fast mobile web experience is essential when most people are accessing websites with their mobile devices. And it’s only becoming more critical now that google takes website loading speed as a ranking factor. Improving/maximizing [crayon-641821165dae0998569688-i/] application performance therefore should be treated as a top priority. Minimize unnecessary re-render This could possibly the most…
-
React async rendering, getting prepared
React async rendering, a new exciting built in feature, is coming in react version 17. While we don’t know the exact time frame, it may well be very soon. For existing projects, most likely you will have some preparation and migration works to finish before you can take advantage of this new cool feature. We finished the migration and sure…
-
route transition for redux-little-router, react ASP.NET Core
[crayon-641821165e407253853134-i/] is a good client side routing library for project that uses [crayon-641821165e40a806844942-i/] and [crayon-641821165e40b636533780-i/]. However, adding transition to the route pages could be tricky. [crayon-641821165e40c140679490-i/] provides a react component [crayon-641821165e40d809509245-i/] for use to define the route pages. Each route page component will be wrapped by a [crayon-641821165e40e911337221-i/] component. As far as I know (after looking at the coding), [crayon-641821165e40f278972683-i/] component will render the route page…
-
Prevent body scrolling for safari/chrome
Prevent body scrolling when showing modal dialog or popup with overlay. Any content in the background should not be moving. That’s because the user actions and experience should focus on the popup/dialog and any movement (scrolling) in the background could cause confusion. And it becomes more annoying when you try to scroll the content of the popup/dialog but ended up it’s…