REPL: importing `'svelte'` returns undefined

[Conduitry]

https://svelte.technology/repl?version=2.6.4&gist=29c93c880013a472c3b079afaa720c2a

The above code works if you download a .zip and run it locally, but in the REPL, after import svelte from 'svelte', svelte is undefined. The inner workings of the REPL's module resolution and bundling are a little mysterious to me, but evidently something is getting confused when importing 'svelte'.

cc @burningTyger

[Conduitry]

Taking a peek at this. This is most peculiar - curl(['https://bundle.run/svelte']) is returning (a promise resolving to) undefined, instead of the module.

If I run

curl.config({ dontAddFileExt: /./ });
curl(['https://bundle.run/svelte']).then(_ => console.log(_))

completely separately from svelte.technology or the REPL, I see the same thing. So it looks like this is an issue with curl.js (or with how packd is bundling svelte?) and not with the REPL.

[Conduitry]

Just including a script tag on a page pointing to 'https://bundle.run/svelte' fails to set window.svelte so I'm thinking this is more likely to be an issue with packd.

Edit: Or maybe Svelte's package.json ought to have a module entry pointing at an ES module build? packd should still be able to handle a commonjs module though.

[Rich-Harris]

Huh. This is actually Rollup's fault, in a way, since it's taking the UMD build from the Svelte package and wrapping that in another UMD build, which would work fine except that it's rewriting this to undefined, per the ESM spec. Adding a pkg.module would be the easiest way to fix this specific case.

[Conduitry]

Interesting. What is packd doing exactly when it is asked to deal with a package with no ES module field? I'm a bit surprised that https://github.com/Rich-Harris/packd/blob/master/package.json doesn't mention rollup-plugin-commonjs. Something has to be happening before Rollup gets the module, because the module isn't an ES6 module and Rollup isn't complaining about it. Rollup treating a top-level this as undefined doesn't really seem like a problem to me - that should be getting handled by someone else, right?