Most React developers use React Hooks to create React apps, as evidenced by documentation, examples, and videos on YouTube.

However, this is not the case in the Microsoft 365 development space, where SharePoint Framework (SPFx) developers still primarily use class components. This is likely due to new SPFx projects defaulting to class components, which have been one of the last holdouts.

Even new Microsoft Teams projects created with YO Teams in the Visual Studio Teams Toolkit use Hooks. Although I was late to switch over to Hooks, I quickly saw why so many others had made the switch. If you haven't made the switch yet, this is for you.

In my article this week, I'll explain why functional components enabled by Hooks are better than class components, and why I prefer Hooks even more. For SPFx developers, I will also show you how to quickly convert your new SPFx web part projects to React Hooks.

That's what this week's article is all about!

🍿 Click Worthy Things

🏆 My Picks

Let's go with a retro theme this week!

  • 🤓 I don't want to date myself, but these retro terminal emulators mimic old cathode displays. Hope someone releases a theme for my preferred terminal using one of these!
  • 🕹️ Atari launched collectible circuit boards for some of their most beloved arcade classics. These 1:1 recreations actually work too! You can use them in the original arcade cabinets, or would be awesome if framed in your office!

The Full Stack Dev's Microsoft 365 Playbook

Andrew, a 19-year recipient of Microsoft's MVP award, helps full-stack developers efficiently build Microsoft 365 apps through pragmatic mentoring and self-paced courses. Join 8,000+ developers and receive his bi-weekly newsletter filled with insights on Microsoft 365 and Azure topics.

Read more from The Full Stack Dev's Microsoft 365 Playbook