deno/cli/npm
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
..
resolution feat: auto-discover package.json for npm dependencies (#17272) 2023-02-20 19:14:06 +01:00
resolvers feat: auto-discover package.json for npm dependencies (#17272) 2023-02-20 19:14:06 +01:00
cache.rs refactor: use deno_graph's semver and npm structs (#17791) 2023-02-15 13:20:40 -05:00
mod.rs feat: auto-discover package.json for npm dependencies (#17272) 2023-02-20 19:14:06 +01:00
registry.rs feat: auto-discover package.json for npm dependencies (#17272) 2023-02-20 19:14:06 +01:00
tarball.rs refactor: use deno_graph's semver and npm structs (#17791) 2023-02-15 13:20:40 -05:00