Recursively fetching entire sub-pages can be…problematic

[nvlgzr]

This has only affected me once: when trying out notion2svelte on a page that I didn't intend to publish.

The full story—for my own future benefit—stats with me wanting to "move" a custom-uploaded cover image from one page to another in my private Notion. The image in question turns out to have no URL, but rather a data:image: data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7. This isn't the entire image, being far too terse, and I don't feel like researching exactly how Notion resolves it into the actual image. Instead, I was curious whether notion2svelte would download a usable image file that I could then re-upload to the new page.

(Side note: it turns out that the data:image comes through the Notion API as a .heic file. Notion doesn't allow these to be uploaded via the desktop app, so I've no idea how I managed to set it in the first place! Anyway…back to the potential problem with recursive fetching…)

The page I was testing happened to have some sub-pages with heavy image counts…mostly imported using the web clipper from other sites (e.g., Tufte). This isn't something I'm likely to do on accident when it comes to actual production use of notion2svelte, but it's worth noting for v2 that this should probably be handled elsewise. ¯\_(ツ)_/¯