ServerJS/Modules/SecurableModules: Difference between revisions

Jump to navigation Jump to search
Removed mention of file system backends
(Added a link to the unit test repository.)
(Removed mention of file system backends)
Line 17: Line 17:
# A module identifier is a String of "terms" delimited by forward slashes.
# A module identifier is a String of "terms" delimited by forward slashes.
# A term must be a camelCase identifier, ".", or "..".
# A term must be a camelCase identifier, ".", or "..".
# The extension of the file corresponding to a module identifier must be inferred by loaders.
# Module identifiers may not have file-name extensions like ".js".
# Module identifiers may be "relative" or "absolute".  A module identifier is "relative" if the first term is "." or "..".
# Module identifiers may be "relative" or "absolute".  A module identifier is "relative" if the first term is "." or "..".
# Absolute identifiers are resolved off the conceptual name space root.  A loader may check multiple roots in a consistent order, like a PATH.
# Absolute identifiers are resolved off the conceptual module name space root.
# Relative identifiers are resolved relative to the file in which "require" is called.
# Relative identifiers are resolved relative to the identifier of the module in which "require" is called.


=== Unspecified ===
=== Unspecified ===
Line 26: Line 26:
This specification leaves the following important points of interoperability unspecified:
This specification leaves the following important points of interoperability unspecified:


# Whether relative module identifiers are supported.
# Whether modules are stored with a database, file system, or factory functions, or are interchangeable with link libraries.
# Whether a PATH is supported by the module loader for resolving module identifiers.
# Whether a PATH is supported by the module loader for resolving module identifiers.


171

edits

Navigation menu