Bypass bot identification systems
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 10.5k
- Forks
- 564
- PR merge metrics
- No merged PRs in 30d
Description
Feature Request
When running wxt in dev mode, chrome is seen as a bot by some websites (like leboncoin.fr that is using datadome). Although this kind of identification is legit, It's quite a blocker when developing extensions locally.
Is your feature request related to a bug?
"N/A"
What are the alternatives?
It's still possible to develop locally by installing built extension by hand on a regular browser (but then losing all the benefits of dev command)
Additional context
Here's what happens when running pnpm dev and using https://leboncoin.fr as a start url:
And being blocked once captcha is resolved manually.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with pnpm dev and the leboncoin.fr start URL, then trace the dev-mode browser-launch path; the issue names no source file or test. Done means an agreed approach addresses bot identification in local development while preserving the benefits of the dev command, with regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, developer-experience, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100