{"id":6039,"date":"2026-04-27T22:02:48","date_gmt":"2026-04-27T22:02:48","guid":{"rendered":"https:\/\/dalelane.co.uk\/blog\/?p=6039"},"modified":"2026-04-27T22:02:48","modified_gmt":"2026-04-27T22:02:48","slug":"how-to-create-a-scratch-extension","status":"publish","type":"post","link":"https:\/\/dalelane.co.uk\/blog\/?p=6039","title":{"rendered":"How to create a Scratch extension"},"content":{"rendered":"

A few years ago, I ran a workshop<\/a> about how to create custom Scratch<\/a> blocks.<\/p>\n

<\/p>\n

I made a template repository<\/a>, based on the Scratch Team repos<\/a>, but with a skeleton extension<\/a> and some extra scripts and automation to handle building and publishing it. I included step-by-step instructions<\/a> for building different types of Scratch extensions, including Scratch blocks based on web APIs, and Scratch blocks based on JavaScript modules from npm<\/a>.<\/p>\n

I created it for educators and coding group volunteers, who would like to customize Scratch for their students by giving them new and unique blocks to make things with. I wanted to make this idea accessible to people who perhaps don’t necessarily think of themselves as developers and wouldn’t otherwise know what it means to clone the Scratch Team repo and start hacking it.<\/p>\n

Scratch has changed a lot in the few years since I first made that, most notably moving from being split across a large number of packages in different repos to a monorepo<\/a>. So this week I gave my setup a bit of a spring-clean to get it up to date<\/a>. <\/p>\n

If you’d like to give it a go, please go to the instructions<\/a> and follow along! (I haven’t updated the screenshots… sorry – github does look a little different since 2023, but I felt that it was close enough to still be understandable<\/strike> was too lazy to re-take all the screenshots. Hopefully that isn’t a blocker.<\/em>) <\/p>\n