12 commits

Author	SHA1	Message	Date
EnokMan	d4f2fda623	fix typos (#3573)	2020-01-02 07:48:46 -05:00
Axetroy	3bb15ceaea	Upgrades rust to 1.40.0 (#3542)	2019-12-23 09:59:44 -05:00
Bartek Iwańczuk	9712e0c315	better error messages for 'relative import path not prefixed with / or ./ or ../' (#3405)	2019-11-26 09:14:04 -08:00
Andy Hayden	f7bbd71e21	Update rust to 1.38.0 (#3030)	2019-10-03 09:16:06 -04:00
Kevin (Kun) "Kassimo" Qian	286ee1d8b6	Fix dynamic import base path problem for REPL and eval (#2757)	2019-08-09 16:33:59 -07:00
Bert Belder	6fbf2e9624	Dynamic import (#2516)	2019-08-09 01:19:45 +02:00
Bartek Iwańczuk	ac269beabe	feat: add debug info to ModuleResolutionError (#2697)	2019-07-30 14:34:57 +00:00
Bert Belder	f4c9b31405	core: replace ModuleSpecifier::to_url() by as_url()	2019-07-08 23:04:07 +02:00
Bartek Iwańczuk	72d9045528	cli: refactor deno_dir to use Url instead of String	2019-07-08 13:07:32 +02:00
Bert Belder	9b1997b8b6	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 13:07:32 +02:00
Bert Belder	32cde32e54	core: return useful error when import path has no prefix like ./	2019-06-30 19:46:32 +02:00
Bartek Iwańczuk	bca5cc5041	Move ModuleSpecifier to //core (#2509)	2019-06-12 16:55:59 -07:00

Renamed from cli/module_specifier.rs (Browse further)