core: clearly define when module lookup is path-based vs URL-based
The rules are now as follows:
* In `import` statements, as mandated by the WHATWG specification,
the import specifier is always treated as a URL.
If it is a relative URL, it must start with either / or ./ or ../
* A script name passed to deno as a command line argument may be either
an absolute URL or a local path.
- If the name starts with a valid URI scheme followed by a colon, e.g.
'http:', 'https:', 'file:', 'foo+bar:', it always interpreted as a
URL (even if Deno doesn't support the indicated protocol).
- Otherwise, the script name is interpreted as a local path. The local
path may be relative, and operating system semantics determine how
it is resolved. Prefixing a relative path with ./ is not required.
2019-07-08 03:55:24 -04:00
|
|
|
[WILDCARD]error: Uncaught ImportPrefixMissing: relative import path not prefixed with / or ./ or ../
|
2019-06-19 22:07:01 -04:00
|
|
|
[WILDCARD] js/errors.ts:[WILDCARD]
|
2019-06-18 10:23:06 -04:00
|
|
|
at DenoError (js/errors.ts:[WILDCARD])
|
|
|
|
at maybeError (js/errors.ts:[WILDCARD])
|
|
|
|
at maybeThrowError (js/errors.ts:[WILDCARD])
|
|
|
|
at sendSync (js/dispatch.ts:[WILDCARD])
|
2019-07-17 18:15:30 -04:00
|
|
|
at fetchSourceFile (js/compiler.ts:[WILDCARD])
|
2019-06-18 10:23:06 -04:00
|
|
|
at _resolveModule (js/compiler.ts:[WILDCARD])
|
|
|
|
at js/compiler.ts:[WILDCARD]
|
|
|
|
at resolveModuleNames (js/compiler.ts:[WILDCARD])
|
|
|
|
at resolveModuleNamesWorker ([WILDCARD]typescript.js:[WILDCARD])
|
|
|
|
at resolveModuleNamesReusingOldState ([WILDCARD]typescript.js:[WILDCARD])
|