denoland-deno/tests/specs/run/no_deno_json/code/package.json

{
  "dependencies": {
    "@denotest/check-error": "1.0.0",
    "chalk": "4"
  },
  "devDependencies": {
    "@denotest/cjs-default-export": "1.0.0"
  }
}
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 13:14:06 -05:00			`{`
			`"dependencies": {`
feat: support bare specifier resolution with package.json (#17864) This commit enables resolution of "bare specifiers" (eg. "import express from 'express';") if a "package.json" file is discovered. It's a step towards being able to run projects authored for Node.js without any changes. With this commit we are able to successfully run Vite projects without any changes to the user code. --------- Co-authored-by: David Sherret <dsherret@gmail.com> 2023-02-22 17:21:05 -05:00			`"@denotest/check-error": "1.0.0",`
			`"chalk": "4"`
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 13:14:06 -05:00			`},`
			`"devDependencies": {`
			`"@denotest/cjs-default-export": "1.0.0"`
			`}`
			`}`