provide source map for global js

[mschoch]

I'm serving our IIFE builds as fireproof.iife.js and connect.iife.js respecitvely (both are distributed as an index.global.js in their packages).

As currently shipped they contain the following reference (last line in the file):

//# sourceMappingURL=index.global.js.map

I'm assuming that is what the browser is using to try and load the source map from, and failing.

I think there are 2 issues:

• I don't think we're including the global js map (probably simple fix to include the file, as it is generated)
• Should we rename this something other than index, as that obviously collides when serving these up in a simple manner, which is how they are most commonly used. If not, is it expected that the consumer would rewrite the source mapping URL?

I'd like to have source mappings for these global js files that work easily out of the box.

[jchris]

we should rename to tokens like fireproof and connect-partykit etc