Chrome extension - DomBlockers problem

Author: LukaSK351Created Jul 7, 2026Updated Jul 10, 2026

Hi, I'm using fingerprint in a Chrome extension purely for anonymous user identification to support free-tier usage limits. My extension doesn't use or need the ad-blocker detection feature at all. Unfortunately, Chrome Web Store review flagged my extension for violating their "single purpose" policy, citing the domBlockers/ad-blocker detection code bundled in your library, as well as flagging some base64-obfuscated strings within it as "obfuscated code." Is there a way to:

Exclude the ad-blocker detection module at build/import time (tree-shaking, custom build, or an excludes option), so it doesn't get bundled at all? Or use a lighter/core version of the library that only includes the fingerprint components I actually need (without ad-blocker detection)?

Any guidance would be much appreciated, as this is currently blocking my extension from staying live on the Chrome Web Store. Thanks!

Source: fingerprintjs/fingerprintjs