deno/cli/tools/pm/outdated
David Sherret ea419a6e39
Some checks are pending
ci / pre-build (push) Waiting to run
ci / bench release linux-x86_64 (push) Blocked by required conditions
ci / lint debug macos-x86_64 (push) Blocked by required conditions
ci / lint debug windows-x86_64 (push) Blocked by required conditions
ci / test debug linux-x86_64 (push) Blocked by required conditions
ci / test release linux-x86_64 (push) Blocked by required conditions
ci / test debug macos-x86_64 (push) Blocked by required conditions
ci / test release macos-x86_64 (push) Blocked by required conditions
ci / test debug windows-x86_64 (push) Blocked by required conditions
ci / test release windows-x86_64 (push) Blocked by required conditions
ci / build libs (push) Blocked by required conditions
ci / publish canary (push) Blocked by required conditions
ci / test debug linux-aarch64 (push) Blocked by required conditions
ci / test release linux-aarch64 (push) Blocked by required conditions
ci / test debug macos-aarch64 (push) Blocked by required conditions
ci / test release macos-aarch64 (push) Blocked by required conditions
ci / lint debug linux-x86_64 (push) Blocked by required conditions
feat(BREAKING/fmt): prompt or require deno fmt . when providing no files and no config files discovered (#30623)
When running `deno fmt` with no input paths with no deno.json or
package.json:

* In tty environments, prompts for confirmation.
* In non-tty environments, errors without providing the current
directory (`deno fmt .`).

The reason for this is we had too many complaints of people accidentally
running `deno fmt` in a directory that wasn't a JS project.
2025-09-08 14:28:47 -04:00
..
interactive.rs feat(BREAKING/fmt): prompt or require deno fmt . when providing no files and no config files discovered (#30623) 2025-09-08 14:28:47 -04:00
mod.rs fix: support cjs, cts, mjs, and mts for the --ext flag (#30398) 2025-08-14 12:02:49 -04:00