summaryrefslogtreecommitdiff
path: root/core/module_specifier.rs
AgeCommit message (Collapse)Author
2020-01-02fix typos (#3573)EnokMan
2019-12-23Upgrades rust to 1.40.0 (#3542)Axetroy
2019-11-26better error messages for 'relative import path not prefixed with / or ./ or ↵Bartek Iwańczuk
../' (#3405)
2019-10-03Update rust to 1.38.0 (#3030)Andy Hayden
2019-08-09Fix dynamic import base path problem for REPL and eval (#2757)Kevin (Kun) "Kassimo" Qian
2019-08-09Dynamic import (#2516)Bert Belder
2019-07-30feat: add debug info to ModuleResolutionError (#2697)Bartek Iwańczuk
2019-07-08core: replace ModuleSpecifier::to_url() by as_url()Bert Belder
2019-07-08cli: refactor deno_dir to use Url instead of StringBartek Iwańczuk
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-12Move ModuleSpecifier to //core (#2509)Bartek Iwańczuk