Kyle Simpson

Also interesting issues to address differently from how Rollup behaves: 1. How to handle name conflicts when re-naming won't work? Rollup issues a warning and just drops the duplicate stuff...

> Shouldn't bar be exported as well since it's in the global scope? Or do you expect the user to specify which (only one) global is exported? Yep, it probably...

> I think that answers 1 and 2 Eh... not exactly. You've implied a change to the way the UMD boilerplate works, where it's assuming a destructuring of a namespace...

I was assuming that these two snippets from your previous message were implying what the **UMD boilerplate itself** would be doing, which has destructuring in it: ```js const { MyModule,...

OK, but I thought you were saying those lines themselves were actually *in the UMD boilerplate*, seems like I misunderstood. Let me illustrate the problem this way: If you take...

> I actually saw this as one of the goals of this feature. It *could* be, it's just surprising to me because it's not how UMD's global behavior is typically...

Speaking of links, here's more I found in terms of reading: http://sriku.org/blog/2014/01/25/implementing-csp-channels-using-promises/ http://jlongster.com/Taming-the-Asynchronous-Beast-with-CSP-in-JavaScript http://swannodette.github.io/2013/07/12/communicating-sequential-processes/

Definitely check out @jhusain's stuff.. he has a proposal to TC39 for `async function*`. https://github.com/jhusain/asyncgenerator

* [TLDraw](https://www.tldraw.com/), source: https://github.com/tldraw/tldraw * [PushPin](https://automerge.org/pushpin/), source: https://github.com/automerge/pushpin

other "local-first" app ideas -- actually, "local-only" in that they're only only for your own "personal cloud" of devices -- that I would like to make for showing off socket:...