11 commits

Author	SHA1	Message	Date
David Sherret	147411e64b	feat: npm workspace and better Deno workspace support (#24334) ... Adds much better support for the unstable Deno workspaces as well as support for npm workspaces. npm workspaces is still lacking in that we only install packages into the root node_modules folder. We'll make it smarter over time in order for it to figure out when to add node_modules folders within packages. This includes a breaking change in config file resolution where we stop searching for config files on the first found package.json unless it's in a workspace. For the previous behaviour, the root deno.json needs to be updated to be a workspace by adding `"workspace": ["./path-to-pkg-json-folder-goes-here"]`. See details in https://github.com/denoland/deno_config/pull/66 Closes #24340 Closes #24159 Closes #24161 Closes #22020 Closes #18546 Closes #16106 Closes #24160	2024-07-04 00:54:33 +00:00
David Sherret	0da01c0ca6	refactor: move PackageJson to deno_config (#24348)	2024-06-26 21:24:10 +00:00
David Sherret	d74be0842a	FUTURE: support deno install <alias>@npm:<package> (#24156) ... Closes #23144	2024-06-10 23:56:43 +00:00
David Sherret	3341c50b6a	refactor: don't share reqwest::HttpClient across tokio runtimes (#24092) ... This also fixes several issues where we weren't properly creating http clients with the user's settings.	2024-06-03 21:17:08 +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
nokazn	3d841acf48	fix(cli): avoid deno add and deno vendor errors when deno.json is empty (#23439)	2024-04-18 15:48:15 -04:00
Bartek Iwańczuk	6b95c53e48	feat(add): always produce multiline config file (#23077) ... This commit changes `deno add` to always produce a multiline config file. In v1.41.3: ``` $ mkdir foo $ cd foo $ deno add @std/assert Created deno.json configuration file. Add @std/assert - jsr:@std/assert@^0.220.0 $ cat deno.json { "imports": { "@std/assert": "jsr:@std/assert@^0.220.0" } } ``` Now: ``` $ mkdir foo $ cd foo $ deno add @std/assert Created deno.json configuration file. Add @std/assert - jsr:@std/assert@^0.220.0 $ cat deno.json { "imports": { "@std/assert": "jsr:@std/assert@^0.220.0" } } ```	2024-03-26 17:40:24 -04:00
David Sherret	ad6b00a2bf	chore: enable clippy unused_async rule (#22834)	2024-03-11 23:48:00 -04:00
Nayeem Rahman	01bc2f530e	feat(unstable/pm): support npm packages in 'deno add' (#22715)	2024-03-06 13:24:15 +00:00
Nayeem Rahman	15f5f74eb7	feat(unstable/pm): support version contraints in 'deno add' (#22646)	2024-03-01 21:34:13 +00:00
Bartek Iwańczuk	fb31ae73e4	feat(unstable): deno add subcommand (#22520) ... This commit adds "deno add" subcommand that has a basic support for adding "jsr:" packages to "deno.json" file. This currently doesn't support "npm:" specifiers and specifying version constraints.	2024-02-29 19:12:04 +00:00