Feature Request: templateUrl multiple named template script selection

I am submitting a feature request for an Component directive ‘templateUrl’ #name extension

given an templates.html with

<script name="aScriptTemplate" type="text/template">
    <h1>Angular 2 App with script templates</h1>
</script>
<script name="anotherScriptTemplate" type="text/template">
    <h1>Angular 2 App with multiple script templates</h1>
</script>

and

@Component({
    selector: 'my-app',
    templateUrl: 'templates.html#aScriptTemplate'
})
....

@Component({
    selector: 'my-template,
    templateUrl: 'templates.html#anotherScriptTemplate'
})
....

[Kriskit]

Like @d3lm we have need for bundling our templates into a single URL to reduce the number of template requests. We cannot support AoT as our underlying ASP.NET MVC site is using a proprietary CMS which enables us to edit content in the templates, these can be multi-language and vary depending on client type (desktop/mobile) using a custom UrlResolver.

I don’t think some sort of crazy online process that compiles the templates every time someone updates the content in the CMS would be appropriate. However, being able to specify multiple component templates in a single file would be useful.

[d3lm]

I actually like this feature request. My motivation behind this that I could fetch for example the template for a container component via HTTP. When using an ASP.NET backend, if you request a .cshtml file, that template gets rendered on the server side. I could then include script tags for other templates inside there, which will also be rendered on the server side. So I reduce the amount of HTTP calls tremendously. Only the template for the container is fetched and all sub-templates for inner dumb components is “inlined” via script tags. AoT does not work for server side rendering in combination with a C# backend, does it?