Right, exactly. So naively sending all dependencies wastefully is just
the first step.
> Afaik the more promising path are prefetch hints on the client. E.g. the
client (or initial HTML payload) knows the dependency tree, adds tags
for preloading the required modules, and then the browser can
> If I understand HTTP/2 correctly, this requires more than a server
> that simply has HTTP push, it requires a server that understands how
> to read ES modules and enumerate their dependencies.
Not only that: The server also has to "know" which modules are already
cached by the client (including
I'm asking about a server that, upon request of a `.js` file, knows
how to enumerate the dependency tree based on that file, _then_ HTTP
pushes all the modules at once.
So basically, from the code
```html
On Sat, Oct 10, 2020 at 5:19 PM #!/JoePea wrote:
> It's 5 years later, but still no (obvious) sign of HTTP/2 servers
> specialized in ES Module push.
>
What does it mean to specialize in module push? How can modules be pushed
without the browser requesting them? Is it a server that reads the
It's 5 years later, but still no (obvious) sign of HTTP/2 servers
specialized in ES Module push.
Do any exist? Anyone have a list? I'm especially interested in the
self-hostable servers, but also curious about solutions where we may
publish modules to.
The non-self-hosted solutions may be
Replies interspersed below
On Thu, Apr 23, 2015 at 9:48 AM, James Burke jrbu...@gmail.com wrote:
On Thu, Apr 23, 2015 at 7:47 AM, Domenic Denicola d...@domenic.me wrote:
Indeed, there is no built-in facility for bundling since as explained
in this thread that will actually slow down your
*To:* Frankie Bagnardi; Matthew Phillips
*Cc:* es-discuss
*Subject:* Re: Re: Are ES6 modules in browsers going to get loaded
level-by-level?
So just to clarify, when browsers support es6 modules we will still need
some extra library to bundle the modules? This would mean es6 modules are
only
23, 2015 10:25
To: Frankie Bagnardi; Matthew Phillips
Cc: es-discuss
Subject: Re: Re: Are ES6 modules in browsers going to get loaded level-by-level?
So just to clarify, when browsers support es6 modules we will still need some
extra library to bundle the modules? This would mean es6 modules
In 10 years, we probably won't be using tools for the modules added in
ES2015, but we might be using them for the changes made in ES2020.
On Thu, Apr 23, 2015 at 7:24 AM, Eric B neuros...@gmail.com wrote:
So just to clarify, when browsers support es6 modules we will still need
some extra
So just to clarify, when browsers support es6 modules we will still need
some extra library to bundle the modules? This would mean es6 modules are
only a syntactical addition and not something functional?
On Thu, Apr 23, 2015 at 10:18 AM Frankie Bagnardi f.bagna...@gmail.com
wrote:
Matthew,
*Subject:* Re: Re: Are ES6 modules in browsers going to get loaded
level-by-level?
So just to clarify, when browsers support es6 modules we will still need
some extra library to bundle the modules? This would mean es6 modules are
only a syntactical addition and not something functional
Matthew, there are already tools for es6 modules + bundling (e.g. babel +
webpack), or converting es6 modules to AMD (e.g. babel
https://babeljs.io/docs/usage/modules/).
On Wed, Apr 22, 2015 at 7:10 PM, Matthew Phillips matt...@bitovi.com
wrote:
Can you clarify what you mean about bundling?
Correct, ES6 has no plans for a bundling solution and the whatwg group
working on the loader has not proposed one.
Nevertheless bundling solution is easier to build and specify. In ES6,
given a root module you can compute the (static) dependency graph as the
basis for creating a bundle. The
On Thu, Apr 23, 2015 at 7:47 AM, Domenic Denicola d...@domenic.me wrote:
Indeed, there is no built-in facility for bundling since as explained in
this thread that will actually slow down your performance, and there’s no
desire to include an antipattern in the language.
Some counterpoint:
Bagnardi; Matthew Phillips
*Cc:* es-discuss
*Subject:* Re: Re: Are ES6 modules in browsers going to get loaded
level-by-level?
So just to clarify, when browsers support es6 modules we will still need
some extra library to bundle the modules? This would mean es6 modules are
only a syntactical
*Subject:* Re: Re: Are ES6 modules in browsers going to get loaded
level-by-level?
So just to clarify, when browsers support es6 modules we will still need
some extra library to bundle the modules? This would mean es6 modules are
only a syntactical addition and not something functional?
On Thu
:* Thursday, April 23, 2015 10:25
*To:* Frankie Bagnardi; Matthew Phillips
*Cc:* es-discuss
*Subject:* Re: Re: Are ES6 modules in browsers going to get loaded
level-by-level?
So just to clarify, when browsers support es6 modules we will still need
some extra library to bundle the modules
Can you clarify what you mean about bundling? Unless I've missed something,
the ES6 module system does not have a story for bundling at all. Of course
formats can be invented in userland but I'm not sure that they are any
easier to implement than say AMD's. I might have missed something though,
18 matches
Mail list logo