Guy Bedford

Here's another question - can the sites table itself map to non-normalized URLs? ``` javascript site({ "jquery": "lib/jquery.js" }); ``` Where the assumption is that the target is just normalized...

Note that with the new spec changes, we treat module specifiers identically to URLs - that is that `./lib/jquery.js` normalizes the same as `lib/jquery.js` the only difference with loading `jquery`...

The sites table acts as a first pass match, falling back to standard URL normalization. So if it matches the sites table is the answer (that is for an entry...

Thanks @caridy that sounds great. To clarify the edge case - say there was a mapping: ``` javascript System.site({ "lib/*": "./static/lib/*.js" }); ``` Would I be right in thinking that...

@matthewp it's the same thing under a different name.

The implementation of sites is near identical to what was implemented for paths in the previous polyfill work.

What is the status on wildcards being supported in the sites table? I have an implementation, but don't want to be setting the wrong expectations for users either. (Implementation at...

@caridy @dherman I'd still be very interested to hear about the status of wildcards in the sites table. It is one of the blocking issues we have at https://github.com/ModuleLoader/es6-module-loader/issues/381 in...

Ok, here's the argument (a) against wildcards in sites, and (b) asking what might replace it. #### (a) Why wildcards should not be in sites The wildcard proposal would be...

The other alternative is always to just accept these behaviors of wildcard paths and implement anyway as well.