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

Age	Commit message (Collapse)	Author
2024-08-31	chore: remove DENO_FUTURE=1 from spec tests (#25329)	Bartek Iwańczuk
	Towards https://github.com/denoland/deno/issues/25241
2024-08-30	refactor: remove DENO_FUTURE (#25314)	David Sherret

2024-08-29	feat(config): Node modules option for 2.0 (#25299)	Nathan Whitaker

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-29	fix(cli): Prefer npm bin entries provided by packages closer to the root ↵	Nathan Whitaker
	(#24024) Fixes #24012. In the case of multiple packages providing a binary with a same name, we were basically leaving the results undefined (since we set up things in parallel, and whichever got set up first won). In addition, we were warning about these cases, even though it's a situation that's expected to occur. Instead, in the case of a collision in the binary names, we prefer the binary provided by the package with the least depth in the dependency tree. While I was at it, I also took moved more code to `bin_entries.rs` since it was starting to get a bit cluttered.