Practical SharePoint Framework (SPFx) Development (Franck Cornu, Anoop T.) (z-library.sk, 1lib.sk, z-lib.sk)

【One-Line Pitch】 A hands-on guide to building modern SharePoint and Microsoft 365 customizations with the SharePoint Framework, taking you from environment setup through web parts, extensions, and Adaptive Card Extensions to testing, upgrades, and community tooling. Best for web developers with JavaScript/TypeScript experience who are new to SPFx, and for on-premises SharePoint developers moving to the cloud. 【Book Arc】 - **Opening (~0%–15%)**: Frames SPFx's place in the Microsoft 365 ecosystem — its evolution away from proprietary extensibility, cloud vs. on-premises differences, and how to choose the right customization type for a business need. - **Early (~15%–35%)**: Establishes the development foundation — environment setup, the general build process, solution structure, and a running Packt product-management use case that threads through later chapters. - **Early–Middle (~35%–55%)**: Builds the core web part experience: creating a web part, wiring services and Microsoft Graph, styling with SASS, theming and dark mode, localization, top actions, and the property pane (default and custom controls). - **Middle (~55%–65%)**: Moves into composition and extensions — connecting web parts, then Application Customizers, Field Customizers, ListView Command Sets, and Search Query Modifiers. - **Late (~65%–75%)**: Covers Adaptive Card Extensions for Viva Connections, plus production concerns: testing with Jest, upgrading solutions, and community tools like PnPjs and PnP React controls. - **Ending (~75%–100%)**: Closes with alternative development platforms (Docker, GitHub Codespaces, WSL, Azure VMs) and the big-picture recap of SPFx capabilities and community resources. 【Key Takeaways】 - **SPFx is a web-stack-first extensibility model** (Opening): it deliberately moves away from proprietary patterns, so React, TypeScript, and standard HTTP APIs carry over directly — lowering the learning curve for web developers. - **Choosing the right customization type is a design decision, not an afterthought** (Early): the book contrasts configuration, low-code, and full custom development so you can match effort to business requirements. - **A single running use case ties the whole book together** (Early–Middle): the Packt product inventory scenario (products, stock levels, dashboards) recurs across chapters, so concepts compound instead of resetting each time. - **The property pane is where web part usability lives** (Early): default controls, validation, custom fields, async handling, and dynamic configuration are treated as first-class skills. - **Extensions extend reach beyond web parts** (Middle): Application Customizers, Field Customizers, ListView Command Sets, and Search Query Modifiers each solve distinct UX problems across sites and lists. - **Adaptive Card Extensions target Viva Connections** (Late): ACEs let you surface and interact with organizational data in the Viva experience, integrated with Microsoft Graph. - **Testing and upgrades are part of shipping** (Late): Jest-based testing and manual/CLI upgrade paths are covered so solutions stay maintainable as SPFx releases evolve. - **The community ecosystem is a force multiplier** (Late): PnPjs, PnP React controls, PnP Modern Search, Dev Proxy, and Fast Serve are presented as practical accelerators. 【Reading Tips】 - **Deep-read the early setup and use-case chapters** — the recurring product scenario pays off only if you follow it from the start. - **Skim the extension chapters if you only need web parts**, but read the "why is it needed / when to use" framing in each, since that's the real decision-making value. - **Treat the property pane and theming/localization sections as reference** — return to them when your own web part needs polish. - **Don't skip testing, upgrades, and community tools** even though they feel like "extra" — they're what separates a demo from a maintainable solution. - **Have a Microsoft 365 developer tenant ready** before starting, since the samples are meant to be run, not just read. 【Coverage Limits】 The excerpts are heavily front-matter and table-of-contents oriented, so chapter-level detail beyond titles and brief descriptions is thin; specific code patterns, figures, and step-by-step instructions are not covered here.