3 commits

Author	SHA1	Message	Date
Bartek Iwańczuk	c94d1b10f8	feat(install): change 'Add ...' message (#24949) ... Changes messages printed by `deno add` from `Add @oak/oak - jsr:@oak/oak^16.1.0` to `Add jsr:@oak/oak16.1.0`.	2024-08-08 16:25:05 +02:00
Nathan Whitaker	795ed23b35	fix(future): Emit deno install warning less often, suggest deno install in error message (#24706) ... Two small changes: - In our BYONM errors, suggest running `deno install` instead of `npm install` if `DENO_FUTURE` is set - Only emit warning about `deno install` changes if you do `deno install <foo>` with deno_future unset	2024-07-24 23:37:13 +00:00
Bartek Iwańczuk	4e23a5b1fc	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 12:34:46 -07:00