Use consistent (two-space) indentation in all tsconfig code blocks

Author: mkantor

packages/tsconfig-reference/copy/en/options/customConditions.md

@@ -10,11 +10,11 @@ For example, when this field is set in a `tsconfig.json` as so:
 
 ```json tsconfig
 {
-    "compilerOptions": {
-        "target": "es2022",
-        "moduleResolution": "bundler",
-        "customConditions": ["my-condition"]
-    }
+  "compilerOptions": {
+    "target": "es2022",
+    "moduleResolution": "bundler",
+    "customConditions": ["my-condition"]
+  }
 }
 ```
 
@@ -24,15 +24,15 @@ So when importing from a package with the following `package.json`
 
 ```jsonc
 {
-    // ...
-    "exports": {
-        ".": {
-            "my-condition": "./foo.mjs",
-            "node": "./bar.mjs",
-            "import": "./baz.mjs",
-            "require": "./biz.mjs"
-        }
+  // ...
+  "exports": {
+    ".": {
+      "my-condition": "./foo.mjs",
+      "node": "./bar.mjs",
+      "import": "./baz.mjs",
+      "require": "./biz.mjs"
     }
+  }
 }
 ```
 

packages/tsconfig-reference/copy/en/options/moduleSuffixes.md

@@ -7,9 +7,9 @@ Provides a way to override the default list of file name suffixes to search when
 
 ```json tsconfig
 {
-    "compilerOptions": {
-        "moduleSuffixes": [".ios", ".native", ""]
-    }
+  "compilerOptions": {
+    "moduleSuffixes": [".ios", ".native", ""]
+  }
 }
 ```
 

packages/tsconfig-reference/copy/en/options/noUncheckedSideEffectImports.md

@@ -22,7 +22,7 @@ Your bundler might be configured in such a way where you can include specific `.
 import "./button-component.css";
 
 export function Button() {
-    // ...
+  // ...
 }
 ```
 

packages/tsconfig-reference/copy/en/options/paths.md

@@ -23,12 +23,12 @@ This would allow you to be able to write `import "jquery"`, and get all of the c
 {
   "compilerOptions": {
     "paths": {
-        "app/*": ["./src/app/*"],
-        "config/*": ["./src/app/_config/*"],
-        "environment/*": ["./src/environments/*"],
-        "shared/*": ["./src/app/_shared/*"],
-        "helpers/*": ["./src/helpers/*"],
-        "tests/*": ["./src/tests/*"]
+      "app/*": ["./src/app/*"],
+      "config/*": ["./src/app/_config/*"],
+      "environment/*": ["./src/environments/*"],
+      "shared/*": ["./src/app/_shared/*"],
+      "helpers/*": ["./src/helpers/*"],
+      "tests/*": ["./src/tests/*"]
     }
   }
 }

packages/tsconfig-reference/copy/en/options/resolveJsonModule.md

@@ -12,9 +12,9 @@ TypeScript does not support resolving JSON files by default:
 // @errors: 2732
 // @filename: settings.json
 {
-    "repo": "TypeScript",
-    "dry": false,
-    "debug": false
+  "repo": "TypeScript",
+  "dry": false,
+  "debug": false
 }
 // @filename: index.ts
 import settings from "./settings.json";
@@ -32,9 +32,9 @@ Enabling the option allows importing JSON, and validating the types in that JSON
 // @moduleResolution: node
 // @filename: settings.json
 {
-    "repo": "TypeScript",
-    "dry": false,
-    "debug": false
+  "repo": "TypeScript",
+  "dry": false,
+  "debug": false
 }
 // @filename: index.ts
 import settings from "./settings.json";

packages/tsconfig-reference/copy/en/options/verbatimModuleSyntax.md

@@ -10,7 +10,7 @@ Basically, if you write something like
 import { Car } from "./car";
 
 export function drive(car: Car) {
-    // ...
+  // ...
 }
 ```
 
@@ -19,7 +19,7 @@ Your output JavaScript might look something like this:
 
 ```js
 export function drive(car) {
-    // ...
+  // ...
 }
 ```
 
@@ -113,9 +113,9 @@ function bar() {}
 function baz() {}
 
 export = {
-    foo,
-    bar,
-    baz
+  foo,
+  bar,
+  baz
 };
 ```
 
@@ -128,9 +128,9 @@ function bar() {}
 function baz() {}
 
 module.exports = {
-    foo,
-    bar,
-    baz
+  foo,
+  bar,
+  baz
 };
 ```