Try loading without the SEA module first, and replace this cell with: `Gun = (await import('https://cdn.skypack.dev/gun@0.2020.1237?min')).default`

@dleeftink, many thanks for the suggestion and for reaching out here. The `(await import( 'https://cdn.skypack.dev/‹packageName›)).default` idiom seems to work well. If I may ask: how would you recommend loading SEA from there? the same way? `SEA = (await import('https://cdn.skypack.dev/gun@0.2020.1237/sea.js?min')).default` Or should I somehow use the `GUN` property that is embedded in the SEA object, to reach out to the GUN module?

I'd say try the [Gunnery](https://github.com/warashibe/gunnery) package, bundling both and giving a slightly simplified interface to authentication. It's usage takes some getting used to, differentiating between authenticated (put, get, on), user (uput, uget, uon) and global space (gput, gget, gon) await functions. The uon/gon functions do not trigger for me, which is why Gunnery is mostly useful when trying to write via an authenticated user created via `publisherKey = Gunnery.user.auth('username', 'password') `and passing this key to uput(pubKey, 'dataKey', 'subKey, {data}), resulting in a nested object in user space as {dataKey:{subKey:{data}}}.

Very interesting, thanks for the hint. Gunnery uses Babel to transform the GUN/SEA source code and provide the missing exports; and then to transpile and to bundle in a single library, that can be consumed as an ES module — if I got it right from a quick read. I'll have a closer look. I guess I have enough material to restart my study; I'm still new to the GUN ecosystem.