denoland-deno/tests/specs/install/future_install_local_deno/deno.json

{
  "imports": {
    "@std/fs/": "https://deno.land/std@0.224.0/fs/",
    "@denotest/esm-basic": "npm:@denotest/esm-basic@^1.0.0",
    "@denotest/add": "jsr:@denotest/add",
    "test-http": "http://localhost:4545/v1/extensionless"
  }
}
FUTURE: `deno install` changes (#23498) This PR implements the changes we plan to make to `deno install` in deno 2.0. - `deno install` without arguments caches dependencies from `package.json` / `deno.json` and sets up the `node_modules` folder - `deno install <pkg>` adds the package to the config file (either `package.json` or `deno.json`), i.e. it aliases `deno add` - `deno add` can also add deps to `package.json` (this is gated behind `DENO_FUTURE` due to uncertainty around handling projects with both `deno.json` and `package.json`) - `deno install -g <bin>` installs a package as a globally available binary (the same as `deno install <bin>` in 1.0) --------- Co-authored-by: Nathan Whitaker <nathan@deno.com> 2024-05-08 15:34:46 -04:00			`{`
			`"imports": {`
			`"@std/fs/": "https://deno.land/std@0.224.0/fs/",`
			`"@denotest/esm-basic": "npm:@denotest/esm-basic@^1.0.0",`
			`"@denotest/add": "jsr:@denotest/add",`
			`"test-http": "http://localhost:4545/v1/extensionless"`
			`}`
			`}`