-
-
Notifications
You must be signed in to change notification settings - Fork 795
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
Starting inspector on 127.0.0.1:9229 failed: address already in use #2975
Labels
Comments
Thanks for reporting. It looks like this issue might be related: vercel/next.js#11030, and we also pass the I guess that will be solved when we migrate out CLI package to nextjs fork: blitz-js/legacy-framework#391. |
should be resolved with blitz 2.0 |
blitzjs-bot
added
status/done
and removed
status/ready-to-work-on
This issue is up for grabs
labels
Aug 29, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the problem?
I read this document (https://blitzjs.com/docs/troubleshooting#chrome-devtools-server) and try to debug blitz app with DevTool, but this looks like it is not working correctly.
Paste all your error logs here:
Paste all relevant code snippets here:
What are detailed steps to reproduce this?
NODE_OPTIONS='--inspect' blitz dev
Run
blitz -v
and paste the output here:Please include below any other applicable logs and screenshots that show your problem:
No console on DevTool:
Blitz.js in Thread section:
No Blitz application inside the Remote Target section:
The text was updated successfully, but these errors were encountered: