You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I can gather, the current consensus is for module keys to be absolute URLs. Ignoring the issue of URLs vs module identifiers, is there at least agreement that the paths are separated by forward slashes?
The text was updated successfully, but these errors were encountered:
For dynamic loading, developers will want to rely on string manipulation libraries for constructing module specifiers. In tools that iterate over the loaded modules, the keys will need to be converted into values that can be fetched. Of course the internal format of the keys should not be part of the spec, but the API should dictate the form of module specifiers, any other inputs to the names, and the format of keys coming back out. Specifying forward slashes would be a great help to developers with almost no cost and few downsides in practice.
As far as I can gather, the current consensus is for module keys to be absolute URLs. Ignoring the issue of URLs vs module identifiers, is there at least agreement that the paths are separated by forward slashes?
The text was updated successfully, but these errors were encountered: