deno.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2024-10-18	fix(npm): ensure scoped package name is encoded in URLs (#26390)	Marvin Hagemeister
	Fixes https://github.com/denoland/deno/issues/26385
2024-08-21	fix(add): Handle packages without root exports (#25102)	Nathan Whitaker
	Fixes #24607. This PR makes the logic that caches top level dependencies (things present in import map) smarter, so we handle JSR dependencies without root exports.
2024-07-24	fix(future): Emit `deno install` warning less often, suggest `deno install` ↵	Nathan Whitaker
	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-05-16	perf(jsr): download metadata files as soon as possible and in parallel (#23836)	David Sherret
	* https://github.com/denoland/deno_graph/pull/471 * https://github.com/denoland/deno_graph/pull/473
2024-05-08	FUTURE: `deno install` changes (#23498)	Bartek Iwańczuk
	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>