summaryrefslogtreecommitdiff
path: root/tests/error_011_bad_module_specifier.ts.out
AgeCommit message (Collapse)Author
2019-07-08core: clearly define when module lookup is path-based vs URL-basedBert Belder
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-06-30core: return useful error when import path has no prefix like ./Bert Belder
2019-06-19Combine CLI Errors (#2487)Kitson Kelly
2019-06-18fix: use Loader::resolve in op_fetch_module_meta_data (#2519)Bartek IwaƄczuk