Multiple Imports withing the same import() about systemjs

[MajorBreakfast]

I use this in my app:

Promise.all([
    System.import('module1'),
    System.import('module2')
  ])
  .then(function(modules) { ... })

Alternatively:

function multiImport(modules) {
  return Promise.all(modules.map(function(m) { return System.import(m) }))
}

+1 @guybedford @robdodson Array support for System.import would be convenient when combining SystemJS and Web Components.

[probins]

https://groups.google.com/forum/#!topic/jspm-io/rQd_XT_ZetU

[guybedford]

Yes, this is supported, but it is undocumented as I'm still not sure if the Loader specification will allow this or not.

Even if not in the spec though, I would still add it to jspm. But it then just depends how possible that is.

[AlessandroEmm]

Thank you guys, worked like a charm!

May I ask how much work it would be to remove the functionality for npm, github and cdnJS? As for an internal web application I can't anyway rely on them so I'd rather save the few KB's if possible.

[guybedford]

The endpoints are simply this line here - https://github.com/jspm/jspm-loader/blob/master/loader.js#L811

It's just a default. There is really nothing to remove.

You may want to set a custom registryURL as well.

Any further questions just ask.

[robdodson]

@guybedford is this still supported? I was looking to do the same thing this weekend but wasn't sure how to make the jspm object available on my page

[robdodson]

@MajorBreakfast yeah I wrote something similar, was just curious if there is some way to not have to do all the boilerplate myself. I think (but I may be mistaken) that System usually wants there to just be 1 call to import (like for a main.js file) and so maybe this is outside normal usage. @guybedford is that accurate?

[guybedford]

@robdodson I don't know of any plans for an array require, but it could be worth bringing up as a spec issue. I do like the perspective of having a single entry point though, as you then need all dynamic calls to be full modules themselves, which works well with bundling. We will have <script type="module"> to make the inline case easier anyway in future.

[robdodson]

@guybedford yeah I'm specifically looking at it from the case of Web Components where it's harder to have one entry point if you're using HTML Imports. I'm not a fan of the current approach in ModuleLoader/es-module-loader#95 with htmlimport-esmodule, I'd love to just System.import whatever I need in my script tags vs having to include an HTML Import and then an import statement which references the url for the import. That approach just feels cumbersome to me.

[guybedford]

@robdodson Erik's proposal is out of date, I've updated ModuleLoader/es-module-loader#95 to reflect the latest information. It's worth thinking in terms of module tags first, then working backwards to System.import.

[bennycode]

I tried to use it this way:

System.import(['dexie', 'proteus'])
.then(function(dexie, proteus) {
  console.log('dexie', dexie);
  console.log('proteus', proteus);
});

But all I'm getting is:

system.src.js:1226 Uncaught (in promise) TypeError: e.match is not a function(…)