doc-detective 2.18.0 → 2.19.0-dev.0

package/.github/workflows/npm-test.yaml

@@ -27,15 +27,16 @@ jobs:
         node: 
           - 18
           - 20
+          - 22
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
 
-      - uses: actions/setup-node@v3
+      - uses: actions/setup-node@v4
         with:
           node-version: ${{ matrix.node }}
 
       - name: Cache node_modules
-        uses: actions/cache@v3
+        uses: actions/cache@v4
         with:
           # Cache key uses the contents of `package-lock.json` to identify unique cache
           key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}

package/README.md

@@ -33,14 +33,7 @@ Doc Detective has multiple components to integrate with your workflows as you ne
 
     If you don't install Doc Detective globally, you'll be prompted to install the first time you run an `npx` command.
 
-## (Optional) Get sample files
-
-To test a few samples, clone the repo and navigate to the `samples` directory:
-
-```bash
-git clone https://github.com/doc-detective/doc-detective.git
-cd doc-detective/samples
-```
+    **Note:** If you're working in a cloned `doc-detective` repository, run `npm i` to install local dependencies or the `npx` command in the next step will fail.
 
 ## Run tests
 
@@ -70,6 +63,10 @@ You can override config options with command-line arguments. For example, to run
 npx doc-detective runTests --config .doc-detective.json --input tests.spec.json
 ```
 
+### Check out some samples
+
+You can find test and config samples in the [samples](https://github.com/doc-detective/doc-detective/tree/main/samples) directory.
+
 ## Check your test coverage
 
 You can check the test coverage of your documentation source files with the `runCoverage` command, specifying the source file or directory of source files with the `--input` argument. Doc Detective identifies potential areas of test coverage with file-format-specific regex, and supports CommonMark syntax natively. If you want to test coverage of a file with different syntax, update the `fileTypes` object of your [config](https://doc-detective.com/docs/references/schemas/config.html) file accordingly.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "doc-detective",
-  "version": "2.18.0",
+  "version": "2.19.0-dev.0",
   "description": "Treat doc content as testable assertions to validate doc accuracy and product UX.",
   "bin": {
     "doc-detective": "src/index.js"
@@ -9,7 +9,9 @@
   "scripts": {
     "mocha": "mocha",
     "test": "mocha test/*.test.js",
+    "prerunTests": "node ./src/checkDependencies.js",
     "runTests": "node ./src/index.js runTests",
+    "prerunCoverage": "node ./src/checkDependencies.js",
     "runCoverage": "node ./src/index.js runCoverage",
     "dev": "node ./dev"
   },
@@ -32,13 +34,13 @@
   "homepage": "https://github.com/doc-detective/doc-detective#readme",
   "dependencies": {
     "@ffmpeg-installer/ffmpeg": "^1.1.0",
-    "doc-detective-common": "^1.21.0",
-    "doc-detective-core": "^2.18.0",
+    "doc-detective-common": "1.22.0-dev.2",
+    "doc-detective-core": "2.19.0-dev.0",
     "prompt-sync": "^4.2.0",
     "yargs": "^17.7.2"
   },
   "devDependencies": {
-    "chai": "^5.1.1",
-    "mocha": "^10.7.3"
+    "chai": "^5.1.2",
+    "mocha": "^11.1.0"
   }
 }

package/samples/.doc-detective.json

@@ -65,6 +65,7 @@
           "regex": ["!\\[.+?\\]\\((.+?)\\)"],
           "actions": [
             {
+              "id": "reference",
               "action": "saveScreenshot",
               "maxVariation": 5,
               "overwrite": "byVariation"

package/samples/doc-content-detect.md

@@ -4,7 +4,7 @@
 
 - The landing page discusses what Doc Detective is, what it does, and who might find it useful.
 
-- [Get started](https://doc-detective.com/docs/get-started.html) covers how to quickly get up and running with Doc Detective.
+- [Get started](https://doc-detective.com/docs/get-started/intro) covers how to quickly get up and running with Doc Detective.
 
 - The [references](https://doc-detective.com/docs/category/schemas) detail the various JSON objects that Doc Detective expects for [configs](https://doc-detective.com/docs/references/schemas/config.html), [test specifications](https://doc-detective.com/docs/references/schemas/specification.html), [tests](https://doc-detective.com/docs/references/schemas/test), actions, and more. Open [typeKeys](https://doc-detective.com/docs/references/schemas/typeKeys.html)--or any other schema--and you'll find two sections: **Fields** and **Examples**.
 

package/samples/doc-content-inline-tests.md

@@ -8,9 +8,9 @@
 
 - The landing page discusses what Doc Detective is, what it does, and who might find it useful.
 
-- [Get started](https://doc-detective.com/docs/get-started.html) covers how to quickly get up and running with Doc Detective.
+- [Get started](https://doc-detective.com/docs/get-started/intro) covers how to quickly get up and running with Doc Detective.
 
-  [comment]: # (step {"action":"checkLink", "url":"https://doc-detective.com/docs/get-started.html"})
+  [comment]: # (step {"action":"checkLink", "url":"https://doc-detective.com/docs/get-started/intro"})
 
 - The [references](https://doc-detective.com/docs/category/schemas) detail the various JSON objects that Doc Detective expects for [configs](https://doc-detective.com/docs/references/schemas/config.html), [test specifications](https://doc-detective.com/docs/references/schemas/specification.html), [tests](https://doc-detective.com/docs/references/schemas/test), actions, and more. Open [typeKeys](https://doc-detective.com/docs/references/schemas/typeKeys.html)--or any other schema--and you'll find two sections: **Fields** and **Examples**.
 

package/src/checkDependencies.js

@@ -0,0 +1,84 @@
+#!/usr/bin/env node
+
+const path = require("path");
+const fs = require("fs");
+const readline = require("readline");
+
+// Check if package.json exists, and if it's for doc-detective
+if (fs.existsSync(path.resolve(process.cwd(), "package.json"))) {
+  try {
+    const json = JSON.parse(
+      fs.readFileSync(path.resolve(process.cwd(), "package.json"))
+    );
+    if (json.name === "doc-detective") {
+      // Check if dependencies are installed
+      checkDependencies();
+    }
+  } catch (error) {
+    console.error(`Failed to parse package.json: ${error.message}`);
+  }
+}
+
+// Check if dependencies are installed
+function checkDependencies() {
+  if (!fs.existsSync(path.resolve(process.cwd(), "node_modules"))) {
+    const rl = readline.createInterface({
+      input: process.stdin,
+      output: process.stdout,
+    });
+
+    // Handle SIGINT (Ctrl+C)
+    rl.on('SIGINT', () => {
+      console.log('\nOperation cancelled by user');
+      rl.close();
+      process.exit(0);
+    });
+
+    rl.question(
+      "It looks like you haven't installed the local dependencies yet. Would you like to install them now? (yes/no): ",
+      (answer) => {
+        const normalizedAnswer = answer.toLowerCase().trim();
+        if (normalizedAnswer === "yes" || normalizedAnswer === "y") {
+          console.log("Installing dependencies. This may take a few minutes.");
+          const { spawn } = require("child_process");
+          const npmCmd = process.platform === 'win32' ? 'npm.cmd' : 'npm';
+          const install = spawn(npmCmd, ["install"], { 
+            stdio: "inherit",
+            shell: true 
+          });
+
+          // Set timeout
+          const timeout = setTimeout(() => {
+            console.error('Installation timed out after 5 minutes');
+            install.kill();
+            rl.close();
+          }, 5 * 60 * 1000);
+
+          install.on("close", (code) => {
+            clearTimeout(timeout);
+            if (code !== 0) {
+              console.error(
+                `Failed to install dependencies (exit code ${code}). Try running 'npm install' manually and check for errors.`
+              );
+              process.exit(1);
+            } else {
+              console.log("Dependencies installed successfully.");
+            }
+            rl.close();
+          });
+
+          install.on("error", (error) => {
+            clearTimeout(timeout);
+            console.error(`Failed to start 'npm install': ${error.message}`);
+            rl.close();
+            process.exit(1);
+          });
+        } else {
+          console.log("Dependencies not installed. Please run 'npm install' manually before proceeding.");
+          rl.close();
+          process.exit(1);
+        }
+      }
+    );
+  }
+}

package/test/artifacts/doc-content.md

@@ -6,8 +6,8 @@
 [comment]: # (step {"action":"goTo", "url":"https://doc-detective.com"})
 
 -   The landing page discusses what Doc Detective is, what it does, and who might find it useful.
--   [Get started](https://doc-detective.com/docs/get-started.html) covers how to quickly get up and running with Doc Detective.
-    [comment]: # (step {"action":"goTo", "url":"https://doc-detective.com/docs/get-started.html"})
+-   [Get started](https://doc-detective.com/docs/get-started/intro) covers how to quickly get up and running with Doc Detective.
+    [comment]: # (step {"action":"goTo", "url":"https://doc-detective.com/docs/get-started/intro"})
 -   The [references](https://doc-detective.com/docs/references/schemas/typeKeys) detail the various JSON objects that Doc Detective expects for configs, test specifications, tests, actions, and more. Each object schema includes an object description, field definitions, and examples.
     [comment]: # (step {"action":"goTo", "url":"https://doc-detective.com/docs/references/schemas/typeKeys"})
     [comment]: # (step {"action":"find", "selector":"h2#fields", "matchText":"Fields"})