Caridy Patiño
Caridy Patiño
> To counterbalance @johnjbarton, in my ES6 projects I almost never use named imports. same here, you can check the of the packages used in formatjs.io, we use named exports...
+1 on `*.import()` and `*.importAll()` where: - `importAll()` is reflective of `import * as ...` - and `import()` is just sugar on top of `importAll()` as in `*.importAll("./mod.js").then(({ def: default...
> I'm wondering if I should exclude it or not. exclude it. > Whatever the state of the document is, making its status clear (in the spec itself) would be...
part of this is now solved by `import()` and imports map. the other part will be feed into the realms proposal.
@ericf `... from this module;` is up in the air, definitely not in ES6.
_update: we need to reach out to @erights to settle this._
Update: - I can't be on Reflect. - System.global: https://github.com/tc39/proposal-global proposal has reached stage 1, and might solve this.
I will take care of this one now that we have the build in place.
> (1) conditionally use code if it is present. Are you talking about polyfills by any chance? Who is responsible for importing the code in the first place? > (2)...
I will discuss the use-case with other folks in upcoming weeks, but for me, it smells. Think about how do you do this today with scripts only? And work your...