-
Notifications
You must be signed in to change notification settings - Fork 776
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: unstable_dev inspect and inspector_port appear not to work #2453
Comments
If you could provide a minimal repro, maybe with Hono, that would help immensely to get to it sooner. |
We're going to close this for now, but feel free to comment here with a minimal reproduction and we can investigate further. It's also possible this has been fixed in recent versions of Wrangler, as |
Hi @penalosa , Commented on wrong issue before.I am actually running into the same issue. The reproduction is quite simple. This is on wrangler 3.4
Trying to connect using devtools will not work. Running I am trying to see where |
I am also having this issue, on Linux. |
As an update, using Wrangler v3 (which uses |
@penalosa still having this issue even with latest wrangler commit dc16f4e, here is a repro: Test (vitest)import { describe, expect, it } from 'vitest'
import { unstable_dev } from 'wrangler'
describe('Unstable Dev No Inspector Test', () => {
it('should open inspect on custom port', async () => {
const worker = await unstable_dev('src/worker.ts', {
inspect: true,
inspectorPort: 10000,
ip: '127.0.0.1', //Just to make sure IPv6 isn't used
})
console.log(worker.address)
console.log(worker.port)
const x = await worker.fetch('index.json')
expect(true).toBeTruthy()
})
}) Notes
|
What version of
Wrangler
are you using?2.6.2
What operating system are you using?
Windows
Describe the Bug
netstat
never shows 39929 opening even when pausing the debugger or leaving a long wait in the test. This is preventing me from debugging inside of unstable_dev and makes it much less useful. I usehono
router in front of it and tend to use that instead so I can debug inside the "worker" itself, I would like to be able to useunstable_dev
in vscode for this howeverSuccess Criteria
Be able to set a breakpoint within Visual Studio code using a test in vitest with unstable_dev and have it pause on the breakpoint inside the worker when calling
fetch
The text was updated successfully, but these errors were encountered: