diff --git a/docs/rules.md b/docs/rules.md
index 64e0107e..75bfbec5 100644
--- a/docs/rules.md
+++ b/docs/rules.md
@@ -90,9 +90,9 @@ Implementation rule behind the ts_project macro.
## validate_options
-validate_options(name, allow_js, composite, declaration, declaration_map, emit_declaration_only,
- extends, incremental, preserve_jsx, resolve_json_module, source_map, target,
- ts_build_info_file, tsconfig, validator)
+validate_options(name, allow_js, composite, declaration, declaration_map, deps,
+ emit_declaration_only, extends, incremental, preserve_jsx, resolve_json_module,
+ source_map, target, ts_build_info_file, tsconfig, validator)
Validates that some tsconfig.json properties match attributes on ts_project.
@@ -108,6 +108,7 @@ Validates that some tsconfig.json properties match attributes on ts_project.
| composite | https://www.typescriptlang.org/tsconfig#composite | Boolean | optional | False |
| declaration | https://www.typescriptlang.org/tsconfig#declaration | Boolean | optional | False |
| declaration_map | https://www.typescriptlang.org/tsconfig#declarationMap | Boolean | optional | False |
+| deps | - | List of labels | required | |
| emit_declaration_only | https://www.typescriptlang.org/tsconfig#emitDeclarationOnly | Boolean | optional | False |
| extends | https://www.typescriptlang.org/tsconfig#extends | Label | optional | None |
| incremental | https://www.typescriptlang.org/tsconfig#incremental | Boolean | optional | False |
@@ -211,7 +212,7 @@ Any code that works with `tsc` should work with `ts_project` with a few caveats:
| ts_build_info_file | The user-specified value of tsBuildInfoFile from the tsconfig. Helps Bazel to predict the path where the .tsbuildinfo output is written. | None |
| tsc | Label of the TypeScript compiler binary to run. This allows you to use a custom compiler. | "@npm_typescript//:tsc" |
| tsc_worker | Label of a custom TypeScript compiler binary which understands Bazel's persistent worker protocol. | "@npm_typescript//:tsc_worker" |
-| validate | Whether to check that the tsconfig JSON settings match the attributes on this target. Set this to False to skip running our validator, in case you have a legitimate reason for these to differ, e.g. you have a setting enabled just for the editor but you want different behavior when Bazel runs tsc. | True |
+| validate | Whether to check that the dependencies are valid and the tsconfig JSON settings match the attributes on this target. Set this to False to skip running our validator, in case you have a legitimate reason for these to differ, e.g. you have a setting enabled just for the editor but you want different behavior when Bazel runs tsc. | True |
| validator | Label of the tsconfig validator to run when validate = True. | "@npm_typescript//:validator" |
| declaration_dir | String specifying a subdirectory under the bazel-out folder where generated declaration outputs are written. Equivalent to the TypeScript --declarationDir option. By default declarations are written to the out_dir. | None |
| out_dir | String specifying a subdirectory under the bazel-out folder where outputs are written. Equivalent to the TypeScript --outDir option. Note that Bazel always requires outputs be written under a subdirectory matching the input package, so if your rule appears in path/to/my/package/BUILD.bazel and out_dir = "foo" then the .js files will appear in bazel-out/[arch]/bin/path/to/my/package/foo/*.js. By default the out_dir is '.', meaning the packages folder in bazel-out. | None |