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
[Bug]: use manifest V3 .When the file(manifest.json) carries ”content_scripts“,puppeteer.launch timeout #12335
Comments
This issue has an outdated Puppeteer version: |
I am not able to reproduce (not enough information), please provide a minimal example that includes all files that are required to run the script (feel free to publish a repository with the reproduction). |
Seeing the same thing |
The directory structure is as follows:
The specific content is as follows:
Uncomment “content_scripts”,will see
|
@Lightning00Blade could you please try to repro with the steps above? |
+1 seeing this as well |
+1 I am seeing this as well brother. |
Greetings, We at Thank you kindly,
|
Wow very insightful, will be trying this immediately! appretiate your hard work and dedication |
Thank you.
|
HMMMMMM had some issues using your advice, and was unable to fix this issue. it still evades me how we will get this working. Dylan
|
Greetings, Our inspect.xyz tech lead was unable to resolve this issue In Production only locally by pointing to their local version.
Thank you kindly,
|
you have lead me astray - but will use this to help guide me to a resolution, thank you Dylan (they/them)
|
+1 seeing this as well |
Willing to paypal $40 for anyone that can fix this or help us fix this |
@Lightning00Blade or @OrKoN I am also willing to send $100 usd to have this issue fixed |
Not able to reproduce:
The following works:
P.S. background permission is not required |
Minimal, reproducible example
Error string
Timed out after 30000 ms while waiting for the WS endpoint URL to appear in stdout!
Bug behavior
Background
chrome version is
Google Chrome 124.0.6367.78
Expectation
.
Reality
puppeteer.launch timeout
Puppeteer configuration file (if used)
No response
Puppeteer version
22.7.0
Node version
20.12.2
Package manager
npm
Package manager version
10.5.0
Operating system
Linux
The text was updated successfully, but these errors were encountered: