issue_674: how to debug rules in AdGuard for Chrome MV3

docs/adguard-browser-extension/mv3-version.md

@@ -13,7 +13,7 @@ The **MV3 version** has replaced our old extension in the [Chrome Web Store](htt
 
 The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf).
 
-The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out.
+The old beta extension was renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out.
 
 ## Main changes in features and settings
 

docs/adguard-browser-extension/solving-problems/debug-rules.md

@@ -13,7 +13,7 @@ These instructions are also meant for problematic cases where you want to modify
 
 1. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager)
 
-1. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install)
+1. **pnpm:** [Install pnpm](https://pnpm.io/installation)
 
 ## How to clone extension
 
@@ -29,30 +29,18 @@ These instructions are also meant for problematic cases where you want to modify
     cd AdguardBrowserExtension
     ```
 
-1. Switch to the `v5.0` branch:
-
-    ```bash
-    git checkout v5.0
-    ```
-
 1. Install dependencies:
 
     ```bash
-    yarn install
+    pnpm install
     ```
 
 ## How to build extension
 
-1. Switch to the `v5.0` branch:
-
-    ```bash
-    git checkout v5.0
-    ```
-
 1. Run the following command in the terminal:
 
     ```bash
-    yarn dev chrome-mv3
+    pnpm dev chrome-mv3
     ```
 
 1. The built extension will be located in the directory:
@@ -79,20 +67,50 @@ That’s it!
 
 ## How to debug rules
 
-1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files.
+For faster development of DNR rulesets, you can use `@adguard/dnr-rulesets` watch mode, which will automatically rebuild rulesets whenever filter files change:
 
-1. Convert the rules from txt to declarative form:
+1. First, build the extension once (just skip, if you did it in the "How to build extension" section):
 
-    ```bash
-    yarn convert-declarative
+    ```shell
+    pnpm dev chrome-mv3
     ```
 
-1. Build the extension again:
+1. Start the watch mode with all required filters:
+
+    ```shell
+    npx @adguard/dnr-rulesets watch \
+        # Force update of rulesets in manifest.json
+        --force-update \
+        # Enable rulesets with IDs 1 and 2
+        --enable=1,2 \
+        # Download filters from the server on the first run
+        --download \
+        # Path to the extension manifest
+        ./build/dev/chrome-mv3/manifest.json \
+        # Path to the filters directory
+        ./build/dev/chrome-mv3/filters \
+        # Path to the web-accessible-resources directory
+        ./Extension/web-accessible-resources \
+        # Output directory for DNR rulesets
+        ./build/dev/chrome-mv3/filters/declarative
+    ```
 
-    ```bash
-    yarn dev chrome-mv3
+    The `--download` flag will download all filters from the server on the first run. For subsequent runs, you can omit this flag to use existing filters:
+
+    ```shell
+    npx @adguard/dnr-rulesets watch \
+        --force-update \
+        --enable=1,2 \
+        ./build/dev/chrome-mv3/manifest.json \
+        ./build/dev/chrome-mv3/filters \
+        ./Extension/web-accessible-resources \
+        ./build/dev/chrome-mv3/filters/declarative
     ```
 
+1. Now, whenever you modify filter files, the DNR rulesets will be automatically rebuilt without having to rebuild the entire extension.
+
 1. Reload the extension in the browser:
 
     ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png)
+
+1. If you see an ❗ mark - it means that assumed rule (which we calculated with our tsurlfilter engine, which performed applying rules in MV2) and actually applied rule (from which we converted to DNR rule) are not the same. And this can be a problem of conversion. <br/> Otherwise, if assumed and applied rules are the same - only applied rule, in raw text and declarative rule views, will be shown.