docs: add command resolution documentation for deno task

runtime/reference/cli/task.md

@@ -98,8 +98,8 @@ Running `deno task "build:*"` will run both `build:client` and `build:server`
 tasks.
 
 For multi-word task names, we recommend using `:` as the separator (e.g.
-`build:client`, `test:unit`, `lint:fix`) to match the convention used in the
-npm ecosystem and to group related tasks for wildcard matching.
+`build:client`, `test:unit`, `lint:fix`) to match the convention used in the npm
+ecosystem and to group related tasks for wildcard matching.
 
 :::note
 
@@ -146,13 +146,13 @@ Dependency tasks are executed in parallel, with the default parallel limit being
 equal to number of cores on your machine. To change this limit, use the
 `DENO_JOBS` environmental variable.
 
-Dependencies are tracked and if multiple tasks depend on the same task, that
-task will only be run once:
+Dependencies are tracked and if multiple tasks depend on the same task, tha task
+will only be run once:
 
 ```jsonc title="deno.json"
 {
   //   a
-  //  / \
+  //  /
   // b   c
   //  \ /
   //   d
@@ -225,7 +225,7 @@ useful to logically group several tasks together:
 
 Running `deno task dev` will run both `dev:client` and `dev:server` in parallel.
 
-## Node and npx binary support
+## Node and npx binary suppor
 
 By default, `deno task` will execute commands with the `deno` binary. If you
 need to ensure that a command is run with the `npm` or `npx` binary, you can do
@@ -239,7 +239,7 @@ so by invoking the `npm` or `npx` `run` command respectively. For example:
 }
 ```
 
-## Workspace support
+## Workspace suppor
 
 `deno task` can be used in workspaces, to run tasks from multiple member
 directories in parallel. To execute `dev` tasks from all workspace members use
@@ -301,8 +301,8 @@ defined tasks.
 
 ### Boolean lists
 
-Boolean lists provide a way to execute additional commands based on the exit
-code of the initial command. They separate commands using the `&&` and `||`
+Boolean lists provide a way to execute additional commands based on the exi code
+of the initial command. They separate commands using the `&&` and `||`
 operators.
 
 The `&&` operator provides a way to execute a command and if it _succeeds_ (has
@@ -409,7 +409,7 @@ hello
 Deno: undefined
 ```
 
-Shell variables can be useful when we want to reuse a value, but don't want it
+Shell variables can be useful when we want to reuse a value, but don't want i
 available in any spawned processes.
 
 ### Exit status variable
@@ -473,34 +473,34 @@ For example, the following redirects _stdout_ of `deno run main.ts` to a file
 called `file.txt` on the file system:
 
 ```sh
-deno run main.ts > file.txt
+deno run main.ts > file.tx
 ```
 
 To instead redirect _stderr_, use `2>`:
 
 ```sh
-deno run main.ts 2> file.txt
+deno run main.ts 2> file.tx
 ```
 
 To redirect both stdout _and_ stderr, use `&>`:
 
 ```sh
-deno run main.ts &> file.txt
+deno run main.ts &> file.tx
 ```
 
 To append to a file, instead of overwriting an existing one, use two right angle
 brackets instead of one:
 
 ```sh
-deno run main.ts >> file.txt
+deno run main.ts >> file.tx
 ```
 
 Suppressing either stdout, stderr, or both of a command is possible by
 redirecting to `/dev/null`. This works in a cross-platform way including on
 Windows.
 
 ```sh
-# suppress stdout
+# suppress stdou
 deno run main.ts > /dev/null
 # suppress stderr
 deno run main.ts 2> /dev/null
@@ -513,15 +513,15 @@ Or redirecting stdout to stderr and vice-versa:
 ```sh
 # redirect stdout to stderr
 deno run main.ts >&2
-# redirect stderr to stdout
+# redirect stderr to stdou
 deno run main.ts 2>&1
 ```
 
 Input redirects are also supported:
 
 ```sh
 # redirect file.txt to the stdin of gzip
-gzip < file.txt
+gzip < file.tx
 ```
 
 Note that redirecting multiple redirects is currently not supported.
@@ -550,7 +550,7 @@ Then on a Windows machine:
 
 ```sh
 > pwd
-C:\Users\david\dev\my_project
+C:\Users\david\dev\my_projec
 > deno task hi
 Hello there!
 ```
@@ -584,7 +584,7 @@ enabled.
 - **nullglob** - When enabled, globs that don't match any files expand to
   nothing instead of the literal glob pattern. Enable with `shopt -s nullglob`.
 - **pipefail** - When enabled, the exit code of a pipeline is the exit code of
-  the last command to exit with a non-zero status, or zero if all commands exit
+  the last command to exit with a non-zero status, or zero if all commands exi
   successfully. Enable with `set -o pipefail`.
 
 Examples:
@@ -639,7 +639,7 @@ box on Windows, Mac, and Linux.
   outputs stdin.
 - [`exit`](https://man7.org/linux/man-pages/man1/exit.1p.html) - Causes the
   shell to exit.
-- [`head`](https://man7.org/linux/man-pages/man1/head.1.html) - Output the first
+- [`head`](https://man7.org/linux/man-pages/man1/head.1.html) - Output the firs
   part of a file.
 - [`unset`](https://man7.org/linux/man-pages/man1/unset.1p.html) - Unsets
   environment variables.
@@ -655,10 +655,72 @@ Note that if you wish to execute any of these commands in a non-cross-platform
 way on Mac or Linux, then you may do so by running it through `sh`:
 `sh -c <command>` (ex. `sh -c cp source destination`).
 
-## package.json support
+## package.json suppor
 
 `deno task` falls back to reading from the `"scripts"` entries in a package.json
 file if it is discovered. Note that Deno does not respect or support any npm
 life cycle events like `preinstall` or `postinstall`—you must explicitly run the
 script entries you want to run (ex.
 `deno install --entrypoint main.ts && deno task postinstall`).
+
+## Command Resolution
+
+When a task command references a binary (e.g., `ohm`, `tsc`, `eslint`), Deno
+resolves it using the following order:
+
+1. **Workspace `node_modules/.bin/`** - If a `node_modules` directory exists
+   (from `deno install` or `deno add`), Deno will look for the binary in
+   `node_modules/.bin/`. This is compatible with how `npx` works in the Node.js
+   ecosystem.
+
+2. **Package.json `bin` field** - When a dependency defines a `bin` field in its
+   `package.json`, Deno automatically makes those commands available within task
+   scripts. This is resolved through Deno's npm compatibility layer.
+
+3. **System PATH** - If the command is not found in `node_modules/.bin/`, Deno
+   falls back to searching the system PATH.
+
+### Example
+
+Given a `package.json` with:
+
+```json
+{
+  "dependencies": {
+    "@ohm-js/cli": "^2.0.0"
+  }
+}
+```
+
+And a `deno.json` with:
+
+```json
+{
+  "tasks": {
+    "generate": "ohm src/grammar.ohm -o src/grammar.js"
+  }
+}
+```
+
+Running `deno task generate` will:
+
+1. Look for `ohm` in `node_modules/.bin/ohm`
+2. If found, execute it using Deno's Node.js compatibility layer
+3. The command runs under Deno's runtime, not Node.js.
+
+### Deno's Equivalent to `npx`
+
+The equivalent of `npx <command>` in Deno is:
+
+```bash
+deno run -A npm:<command>@latest
+```
+
+For example:
+
+- `npx cowsay hello` -> `deno run -A npm:cowsay@latest hello`
+- `npx create-react-app my-app` ->
+  `deno run -A npm:create-react-app@latest my-app`
+
+You can also use `deno add npm:<package>` to add an npm dependency and then
+reference its binaries in `deno task` scripts.