Adguard edge windows 10 расширение

Ad blocker with advanced privacy protection features

AdGuard is a fast and lightweight ad blocking browser extension
that effectively blocks all types of ads and trackers.

Картинка с сайта: github.com

AdGuard is a fast and lightweight ad blocking browser extension that effectively blocks all types of ads and trackers on all web pages. We focus on advanced privacy protection features to not just block known trackers, but prevent web sites from building your shadow profile. Unlike its standalone counterparts (AG for Windows, Mac), the browser extension is completely free and open source. You can learn more about the difference here.

AdGuard does not collect any information about you, and does not participate in any acceptable ads program. The only source of income we have is selling premium versions of our software, and we intend to keep it that way.

• Installation
  • Chrome and Chromium-based browsers
  • Firefox
  • Opera
  • Microsoft Edge
• Contribution
  • Translating AdGuard
  • Testing AdGuard
  • Reporting issues
  • Other options
• Development
  • Requirements
  • How to build
    • Tests and dev build
    • Linking with the developer build of tsurlfilter/tswebextension
    • Building the beta and release versions
    • Special building instructions for Firefox reviewers
    • Analyzing bundle size
    • Debug MV3 declarative rules
  • Linter
  • Update localizations
• Permissions required
• Auto-publish builds
• Minimum supported browser versions

Installation

Chrome and Chromium-based browsers

You can get the latest available AdGuard Extension version from the
Chrome Web Store.

Firefox

You can get the latest version of AdGuard Extension from the
Mozilla Add-ons website.

Opera

Opera is basically a Chromium browser, but it maintains its own add-ons store.
You can get AdGuard Extension from there.

Microsoft Edge

The latest stable version of AdGuard browser extension is available in
Microsoft Store.

Contribution

We are blessed to have a community that does not only love AdGuard, but also
gives back. A lot of people volunteer in various ways to make other users’
experience with AdGuard better, and you can join them!

We, on our part, can only be happy to reward the most active members of the
community. So, what can you do?

Translating AdGuard

If you want to help with AdGuard translations, please learn more about
translating our products here: https://adguard.com/kb/miscellaneous/contribute/translate/program/

Testing AdGuard

You can get a beta version of AdGuard Browser Extension for any browser.
All necessary information on this topic can be found on a
dedicated page on our website.

Reporting issues

GitHub can be used to report a bug or to submit a feature request. To do so, go
to this page
and click the New issue button.

Other options

Here is a dedicated page for those who
are willing to contribute.

Development

Requirements

Ensure that the following software is installed on your computer:

• Node.js: v22 (you can install multiple versions using nvm)
• pnpm: v10
• Git

How to build

Tests and dev build

Install local dependencies by running:

Running unit tests:

Running integration tests:

pnpm test:integration <MODE>
# MODE can be 'dev', 'beta', 'release', same as build targets.

Running integration tests with enabling debug mode (page will be stopped after
tests execution) for one of them:

pnpm test:integration <MODE> [-d <TEST_ID>]
# MODE can be 'dev', 'beta', 'release', same as build targets.
# TEST_ID can be extracted from https://testcases.agrd.dev/data.json

Run the following command to build the dev version:

This will create a build directory with unpacked extensions for all browsers:

build/dev/chrome
build/dev/edge
build/dev/firefox-amo
build/dev/firefox-standalone
build/dev/opera

To make a dev build for a specific browser, run:

Where <browser> is one of the following: chrome, chrome-mv3, edge, opera, firefox,
firefox-standalone, like this:

To run dev build in watch mode, run:

Or for a specific browser:

pnpm dev <browser> --watch

Linking with the developer build of tsurlfilter/tswebextension

Since version v4.0, AdGuard browser extension uses an open source library
tsurlfilter that implements
the filtering engine.

While developing the browser extension it may be required to test the changes
to tsurlfilter. Here’s what you need to do to link your local dev build
to the local dev build of tsurlfilter.

1. Clone and build tsurlfilter libraries.

2. You have two options to link the packages:

   • Option 1: Link the packages globally:

     1. Go to the tsurlfilter/packages/tsurlfilter or tsurlfilter/packages/tswebextension directory.

     2. Run the following command:

        This command will create a symlink to the package in the global node_modules directory.

     3. Once you have the packages linked globally, you can link them to the browser extension.
        Just run the following command in the root directory of the browser extension:

        pnpm link @adguard/tsurlfilter

   • Option 2: Link the packages by path:

     1. Just run the following command in the root directory of the browser extension:

        pnpm link <path-to-tsurlfilter/packages/tsurlfilter>

3. If you want to unlink the packages, just run pnpm unlink @adguard/tsurlfilter
   or pnpm unlink @adguard/tswebextension in the root directory of the browser extension
   regardless of the linking option you chose.

   [!WARNING]
   pnpm will modify the lock file when linking packages. See pnpm/pnpm#4219.

   [!NOTE]
   If you want to list linked packages, run pnpm list --depth 0 in the root directory of the browser extension
   which will show you all dependencies. Linked packages have a version like link:../path/to/package.

4. Build the browser extension in the watch mode:

   pnpm dev <browser> --watch --no-cache

   --no-cache flag is required to rebuild the extension on changes in the linked packages.

Building the beta and release versions

Before building the release version, you should manually download the necessary
resources that will be included into the build: filters and public suffix list.

This command also checks if there are dangerous rules in the filters.
See dangerous rules

You will need to put certificate.pem file to the ./private directory. This
build will create unpacked extensions and then pack them (crx for Chrome).

Special building instructions for Firefox reviewers

1. To ensure that the extension is built in the same way, use the docker image:

   docker run --rm -it \
       -v $(pwd):/workspace \
       -w /workspace \
       adguard/extension-builder:22.14--0.2--0

2. Inside the docker container, install the dependencies:

3. To build the BETA version, run:

   pnpm beta firefox-standalone

4. Navigate to the build directory:

5. Compare the generated firefox.zip file with the uploaded one.

If you need to build the RELEASE version:

1. Run:

2. Navigate to the build directory:

3. Compare the generated firefox.zip file with the uploaded one.

Analyzing bundle size

If you want to analyze the bundle size, run build with the ANALYZE environment:

pnpm cross-env ANALYZE=true pnpm <build command>

So, for example, if you want to analyze the beta build for Chrome, run:

pnpm cross-env ANALYZE=true pnpm beta chrome

Or if you want to analyze all beta builds, run:

pnpm cross-env ANALYZE=true pnpm beta

Analyzer will generate reports to the ./build/analyze-reports directory in the following format:

build/analyze-reports
├── <browser-name>-<build-type>.html

Debug MV3 declarative rules

If you want to debug MV3 declarative rules and check exactly which rules has been applied for some requests, you can build extension in dev mode as described in the upper How to build section, but for specified branch, in which we develop MV3 version.

Then install extension via developer mode, make requests and see applied declarative rules in the filtering log.

How to build MV3 extension

1. Switch to the v5.0 branch:

2. Run the following command in the terminal:

3. The built extension will be located in the directory:

How to install unpacked in the browser

1. Turn on developer mode:

   

   Картинка с сайта: github.com

2. Click Load unpacked:

   

   Картинка с сайта: github.com

3. Select the extension directory and click Select:

   

   Картинка с сайта: github.com

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.

2. Convert the rules from txt to declarative form:

3. Build the extension again:

4. Reload the extension in the browser:

   

   Картинка с сайта: github.com

5. 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.
   Otherwise, if assumed and applied rules are the same — only applied rule (in text and declarative ways) will be shown.

Linter

Despite our code may not currently comply with new style configuration,
please, setup eslint in your editor to follow up with it .eslintrc

Update localizations

To download and append localizations run:

To upload new phrases to crowdin you need the file with phrases
./Extension/_locales/en/messages.json. Then run:

To remove old messages from locale messages run:

To validate translations run:

To show locales info run:

Permissions required

• tabs — this permission is required in order to get the URL of the options page tab
• webRequest — this permission is necessary to apply complicated rules (cosmetic for instance), detecting and removing tracking cookies, counting blocked resources.
• cookies — this permissions is required to delete cookies from requests or changing their lifetime.
• contextMenus — this permission is required in order to create a context menu
• scripting — this permission is required in order to inject assistant script only in the required pages
• storage — this permission is required in order to save user settings, user rules and custom filters
• declarativeNetRequest — this permission is required in order to block, redirect and modify URL requests
• declarativeNetRequestFeedback — this permission is required in order to create a log of the blocked, redirected or modified URL requests
• unlimitedStorage — this permission is required in order to save large filters
• webNavigation — this permission is required in order to catch the moment for injecting scriptlets

Auto-publish builds

Due to the transition from MV2 to MV3, we cannot update our filters remotely. To keep the filters as fresh as possible, we have configured automated tasks in our CI plans. These tasks will build a new version of the extension with only the updated @adguard/dnr-rulesets package, which contains new static rulesets.

These automated tasks will run all necessary checks: unit tests, translation checks, and linter. After that, they will update resources, including filters and local script rules, create a build, and run integration tests to ensure the update is safe.

Finally, the new version of the extension will be published to the Chrome Web Store.

Minimum supported browser versions