7 commits

Author	SHA1	Message	Date
David Sherret	ca51f4f6c0	fix(npm): "not implemented scheme" message should properly show the scheme (#18209)	2023-03-15 15:23:30 -04:00
David Sherret	84bafd11d5	fix: lazily surface errors in package.json deps parsing (#17974) ... Closes #17941	2023-03-03 18:27:05 -04:00
David Sherret	b5b331e31a	fix(npm): skip analyzing more specifiers in package.json (#17938)	2023-02-25 02:16:26 +00:00
David Sherret	5683daf1aa	fix: ignore workspace specifiers in package.json (#17934) ... Part of #17916	2023-02-24 19:27:50 -05:00
David Sherret	6233c0aff0	fix(npm): support bare specifiers in package.json having a path (#17903) ... For example `import * as test from "package/path.js"`	2023-02-23 17:33:23 +00:00
David Sherret	344317ec50	feat(npm): support bare specifiers from package.json in more subcommands and language server (#17891)	2023-02-23 10:58:10 -05:00
Bartek Iwańczuk	4d1a14ca7f	feat: auto-discover package.json for npm dependencies (#17272) ... This commits adds auto-discovery of "package.json" file when running "deno run" and "deno task" subcommands. In case of "deno run" the "package.json" is being looked up starting from the directory of the script that is being run, stopping early if "deno.json(c)" file is found (ie. FS tree won't be traversed "up" from "deno.json"). When "package.json" is discovered the "--node-modules-dir" flag is implied, leading to creation of local "node_modules/" directory - we did that, because most tools relying on "package.json" will expect "node_modules/" directory to be present (eg. Vite). Additionally "dependencies" and "devDependencies" specified in the "package.json" are downloaded on startup. This is a stepping stone to supporting bare specifier imports, but the actual integration will be done in a follow up commit. --------- Co-authored-by: David Sherret <dsherret@gmail.com>	2023-02-20 19:14:06 +01:00