{{asset "bundles"}}

[matthewp]

I don't know why we didn't think of this before @justinbmeyer but we could have a "bundles" asset type that would inline all of the bundles needed for a particular request, so you wouldn't need to wait for steal to progressively fetch them. For example:

<script src="/node_modules/steal/steal.production.js" main="pmo/index.stache!done-autorender"></script>

{{asset "bundles"}}

would render to something like:

<script src="/node_modules/steal/steal.production.js" main="pmo/index.stache!done-autorender"></script>

<script src="/bundles/pmo/index.js"></script>
<script src="/bundles/pmo/home.js"></script>
</script src="/bundles/pmo/home-and-search.js"></script>
<script>
  // Define these as empty to prevent steal from trying to re-import them
  System.set("bundles/pmo/index", {});
  System.set("bundles/pmo/home", {});
  System.set("bundles/pmo/home-and-search", {});
</script>

[matthewp]

For this to work we need Steal to set window.define which it currently does not do.

[matthewp]

An even crazier idea: inline the source code directly in script tags.

[justinbmeyer]

Providing the dep tree would be an easier / safer version that would be only slightly slower.

Sent from my iPhone

On Sep 4, 2015, at 2:56 PM, Matthew Phillips notifications@github.com wrote:

An even crazier idea: inline the source code directly in script tags.

—
Reply to this email directly or view it on GitHub.

[matthewp]

I don't know what would be unsafe about inserting the scripts, this is what steal does anyways, right? The hard part would be getting them in the correct order, so yeah I guess inserting the depCache would be an easier alternative. I'll give it a shot when I have some free time.

[justinbmeyer]

Safer in terms of less error prone, not in terms of security. This is how the old steal worked. It's possible, but tricky.

[matthewp]

The {{asset}} helper no longer exists, and this need is superseded by #211 and #212