ASP.NET Core for Angular, React, Knockout etc developers
summary
Project templates produce Angular/React/Knockout starters that wire up webpack, Hot Module Replacement, webpack Dev middleware and vendoring so live edits keep app state and rebuilds skip 3rd‑party libs. Production builds drop requests from 11 to 8 and download from 3.8MB to 2.1MB; tree‑shaking aims for ~50KB. Server-side prerendering cuts perceived load from ~700ms to 98ms and cached renders to ~3ms. NodeServices runs npm modules server‑side (example: Sharp image resize shrinks 2.5MB to ~10KB) and supports server JS debugging.
AI-written summary · about
chapters (18)
- 0:00Start
- 9:01talk you through the process of creating a project
- 10:02create your new project
- 16:40use webpack to recompile
- 19:06use webpack dev middleware
- 22:25using webpack
- 22:50include source maps in the build
- 23:55run web pack
- 26:19starting up and executing the code on the client
- 37:35the hot module replacement
- 39:09using redux
- 45:00execute javascript code on the server
- 46:23switch over into empty asp net
- 52:29put in any javascript logic
- 54:44debug client-side code using your browser
- 55:47start debugging your server-side code
- 56:20set breakpoints
- 56:40start changing the code in memory without even changing it on disk
related talks
31m10KB or Bust" The Delicate Power of Webpack and Babel"
48mThe Victorian Age of JavaScript
41mOnce you go webpack you never go back
17mRethinking Angular Architecture & Performance
47m2017 DevFestMN Eric Brandes
40mThe state of frontend frameworks in 2023
33mRendering on the Web: Performance Implications of Application Architecture
31mOptimized Angular apps: smaller, faster, better
