Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: Error: failed to find element matching selector "#usm" #3534

Open
dydimos opened this issue Apr 26, 2024 · 0 comments
Open

Error: Error: failed to find element matching selector "#usm" #3534

dydimos opened this issue Apr 26, 2024 · 0 comments

Comments

@dydimos
Copy link

dydimos commented Apr 26, 2024

If I use the cli in WSL2, everything works as expected, if I use the command in Windows, I get the error

Error: Error: failed to find element matching selector "#usm"
at CdpElementHandle.$eval (C:\Users\User1\AppData\Roaming\npm\node_modules\textusm.cli\node_modules\puppeteer-core\lib\cjs\puppeteer\api\ElementHandle.js:423:27)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async CdpFrame.$eval (C:\Users\User1\AppData\Roaming\npm\node_modules\textusm.cli\node_modules\puppeteer-core\lib\cjs\puppeteer\api\Frame.js:414:20)
at async CdpPage.$eval (C:\Users\User1\AppData\Roaming\npm\node_modules\textusm.cli\node_modules\puppeteer-core\lib\cjs\puppeteer\api\Page.js:420:20)
at async C:\Users\User1\AppData\Roaming\npm\node_modules\textusm.cli\dist\index.js:281:19
Internal error.

What could be the problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant