deno.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2023-04-06	refactor(npm): use deno_npm and deno_semver (#18602)	David Sherret

2023-03-15	fix(npm): "not implemented scheme" message should properly show the scheme ↵	David Sherret
	(#18209)
2023-03-03	fix: lazily surface errors in package.json deps parsing (#17974)	David Sherret
	Closes #17941
2023-02-25	fix(npm): skip analyzing more specifiers in package.json (#17938)	David Sherret

2023-02-24	fix: ignore workspace specifiers in package.json (#17934)	David Sherret
	Part of #17916
2023-02-23	fix(npm): support bare specifiers in package.json having a path (#17903)	David Sherret
	For example `import * as test from "package/path.js"`
2023-02-23	feat(npm): support bare specifiers from package.json in more subcommands and ↵	David Sherret
	language server (#17891)
2023-02-20	feat: auto-discover package.json for npm dependencies (#17272)	Bartek Iwańczuk
	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>