> Place all of the code to be exported in 1 file?
that obviously will not work, because of module-scope collision. can
anyone share their experience on deploying a [babel-free] pure-es6
application with 20 es-modules rolled-up into one [production] bundle? is
it even possible?
On Fri, May 31,
> how would i transition from development-mode (20 es-module files) ->
production-mode (1 rollup file)?
Place all of the code to be exported in 1 file?
> with some of them having circular-references
Not certain how that is possible when using ```import``` within
> Oh, and yes, I've loaded upwards of 50-100 modules in development. 20
modules is *easy* to achieve in single-page apps.
was that with some combination of babel/rollup/webpack or pure-es6?
if i want to develop a pure-es6 webapp (no babel), how would i transition
from development-mode (20
On Fri, May 31, 2019 at 2:08 AM Cyril Auburtin
wrote:
> After thinking about it, the dot-notation is maybe confusing, because
>
> ```js
> obj.{a}
> ```
> looks like
> ```js
> obj.a
> ```
> But the results are totally different
>
They are intended to look alike.
The results are not "totally
Where is ```obj``` defined at ```const pickedObj = {...obj: {a, b, c}}```?
On Fri, May 31, 2019 at 9:08 AM Cyril Auburtin
wrote:
> After thinking about it, the dot-notation is maybe confusing, because
>
> ```js
> obj.{a}
> ```
> looks like
> ```js
> obj.a
> ```
> But the results are totally
If it's bundled by Rollup or Webpack into a single bundle, it's
equivalent to a single
After thinking about it, the dot-notation is maybe confusing, because
```js
obj.{a}
```
looks like
```js
obj.a
```
But the results are totally different
Maybe a different syntax might be clearer
```js
obj{a, b, c}
// or
const pickedObj = {...obj{a, b, c}}
// or
const pickedObj = {...obj: {a, b,
7 matches
Mail list logo
