Two new SPFX Realistic bear costumes are coming soon. Help name them and win exclusive TV Bears International prizes

Digital bear designs sculpted in Zbrush become living breathing physical bear costumes brought from screen to reality through expert SFX work

💊Drop #90: Intelligence War AI | SI | Xi | Trump As you are aware Xi travelled to the Whitehouse to meet with Trump for their Summit. Today, President Xi Jinping said, [Pay very close attention to...

Post 4 covered upgrade.md as it exists today. This companion post proposes four concrete, testable extensions — an explicit rollback path when a report can't be fully applied, an incremental strategy for multi-major-version jumps, running the existing test suite as part of verification, and machine-readable JSON output for agent-driven diffing — each framed as a future contribution to SharePoint/spfx-dev-skills, not a criticism of it.

SPFx can call Microsoft Graph, but it can never hold an application permission — a structural fact of the browser execution model that quietly rules out several Microsoft 365 Copilot APIs no matter how the manifest is configured. This post traces the exact rule API by API, shows the documented AadHttpClient-to-backend pattern for everything SPFx can't reach directly, and evaluates SharePoint Copilot Apps — Microsoft's own preview answer to packaging SPFx with Copilot — as the series closes with a design-review checklist and the complete 13-post map.

YouTube video by STREAM WARS

Scaffolding fails safe — a bad attempt just gets deleted. An upgrade runs against a project that already works, so the cost of getting it wrong is much higher. This post walks the spfx-dev-skills upgrade.md reference end to end: the clean-git-state precondition, version detection via .yo-rc.json, the exact m365 spfx project upgrade commands, applying the report in order without overwriting customizations, and the build-clean bar for calling an upgrade done.

Learn the technical lessons of refactoring private SharePoint Framework (SPFx) project code into a reusable NPM package. Explore real-world solutions for PnPjs context coupling, idempotent list provisioning, SHA-256 cryptographic audit hashing, and managing the delicate boundaries of modern TypeScript libraries.

【第57回 Microsoft 365 勉強会】でお話しさせていただいた際の資料です。 SharePointの中でMarkdownをデー...

Post 2 covered create.md as it exists today. This companion post proposes four concrete, testable extensions — scaffold commands for Library and Adaptive Card Extension, a workflow for adding components to an existing solution, the --sharepoint-version flag for on-premises targets, and a post-scaffold validation/commit step — each framed as a future contribution to SharePoint/spfx-dev-skills, not a criticism of it.

Interactive Yeoman prompts are invisible to AI coding agents — they hang, or worse, pick the wrong menu item. This post walks the official spfx-dev-skills create.md reference line by line: environment checks with m365 spfx doctor, the fully flag-based scaffold command for web parts and extensions, dependency install discipline, and toolchain-aware packaging for Heft vs. gulp.