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-65671bfdc57ad897884229-i/], code splitting has become easy with dynamic [crayon-65671bfdc57b1982893414-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 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-65671bfdc7ad2301169815-i/] projects, we have been using [crayon-65671bfdc7ad6674086699-i/] that fits in reasonably well. Recently, I had a chance to hand on evaluating and trying out another router package, [crayon-65671bfdc7ad8695432690-i/]. Both packages are designed with [crayon-65671bfdc7ad9662930258-i/] in mind and so they both work and integrate well with…
-
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-65671bfdc7ef7458202463-i/] application performance therefore should be treated as a top priority. Minimize unnecessary re-render This could possibly the most…
-
route transition for redux-little-router, react ASP.NET Core
[crayon-65671bfdc83bb372930964-i/] is a good client side routing library for project that uses [crayon-65671bfdc83be581771388-i/] and [crayon-65671bfdc83c0695911135-i/]. However, adding transition to the route pages could be tricky. [crayon-65671bfdc83c1469311707-i/] provides a react component [crayon-65671bfdc83c2064848508-i/] for use to define the route pages. Each route page component will be wrapped by a [crayon-65671bfdc83c3741345918-i/] component. As far as I know (after looking at the coding), [crayon-65671bfdc83c4156123929-i/] component will render the route page…
-
React Routing with redux-little-router, ASP.NET Core SPA
React Routing with redux-little-router is part 5 of a 5 parts React with ASP.NET Core series. This series will show you the setup necessary for building React single page application with routing and server-side rendering. For traditional web site that server is responsible to render all web pages, each page change requires browser to request and re-run the page from…