fferent standards, how are companies supposed to
share their own open source code?
> kai zhu
> kaizhu...@gmail.com
>
>
>
> On 9 May 2018, at 8:43 AM, Isiah Meadows wrote:
>
> Missed the list somehow...
>
> -- Forwarded message --
> From: Isiah
On Wed, May 9, 2018 at 9:25 AM, kai zhu
wrote:
> or … we could avoid integration-level headaches that shouldn’t even exist,
> by avoiding es6-modules altogether and
Yes. I talked to my team of average developers, and many were increasingly
of the opinion that they’d all made a big mistake in comi
to tc39’s design-by-commitee process).
kai zhu
kaizhu...@gmail.com
> On 9 May 2018, at 8:43 AM, Isiah Meadows wrote:
>
> Missed the list somehow...
>
> -- Forwarded message --
> From: Isiah Meadows
> Date: Tue, May 8, 2018 at 8:43 PM
> Subject: Re:
Missed the list somehow...
-- Forwarded message --
From: Isiah Meadows
Date: Tue, May 8, 2018 at 8:43 PM
Subject: Re: Dynamic `import` with options
To: Peter Jaszkowiak
Here's three scenarios that aren't even possible without it:
- Hot reloading: https://github.
Yeah, it's about that time. I'm proposing adding support for an
options object as a second "argument" for the call-like `import()`,
something like `import("./foo.mjs", {...options})`. To complement
this, I also propose adding a hook to allow embedders to optionally
return something different from t
5 matches
Mail list logo
