Learn
One subject, split across several parts, followed all the way down. Each series is a curriculum: read it through and you end up able to build the thing yourself.
- What goes in here
- The shipped bundles of five embeddable JavaScript SDKs, fetched and read line by line. What I ran and verified myself is marked apart from what I only assessed from the vendor's own documentation, and chapter 0 of each series says which is which.
- Reading order
- Start at chapter 0. It carries the comparison table and a list of what each chapter covers. After that, jump to the chapter you care about or read straight through. Order only matters for chapter 0.
- How this differs from the blog
- The blog is one post, one subject, done. This section takes the subjects that will not fit in one post. Comparing five SDK designs needs a chapter per design; compressed into one post, every one of them stays at the surface.
Series
1 series / 7 chapters-
How to build a JavaScript SDK: 5 real teardowns
For an SDK customers embed with one script tag, choosing an iframe or DOM injection mostly settles versioning and whether you need postMessage. Five real SDK bundles across six decisions, narrowed down to the one that fits you.
CONTENTS- 0 How to build a JavaScript SDK: 5 real teardowns
- 1 YouTube iframe API: what 993 bytes actually ship
- 2 Iframe isolation and CSP nonces: Safie's 2.61 MB body
- 3 postMessage contracts: Vimeo, YouTube, Safie compared
- 4 cache-control and version pinning: 5 SDKs split two ways
- 5 Web Components vs data attributes: 3 SDK init styles
- 6 Build your own embed SDK: a chat widget in 6 decisions
More series, and more chapters per series, are published in Japanese at kenimoto.dev/ja/learn.