Flo

Also worth mentioning: vscode recently updated to nodejs 18. It's not the first issue caused by that update.

> As it still works with nuxt 3.6, It took a while to process this bit... do you mean nuxt 3.6 works fine with the current vscode release?

I was able to trace the issue down to ```text root@463d9cf38f77:/workspaces/nuxt# git bisect bad abd5d857705fa830d6ef019cb8a5ed3c763b7cd5 is the first bad commit commit abd5d857705fa830d6ef019cb8a5ed3c763b7cd5 Author: Daniel Roe Date: Fri Aug 25 16:20:32...

I'm not sure if I can bisect my way through that one without having a direct check... I'd need a way to distinguish between bad because our issue and bad...

Hello @pi0 and good morning, since I'm no developer - can you tell me in a handful of steps how I can replace the cli in my nuxt development version...

I reported the [ipv6 issue in vscode](https://github.com/microsoft/vscode/issues/191945) a while ago and it was already fixed. This shouldn't matter anymore at least for vscode features. If nuxt listens on ipv6, that...

Hey @amritk - thanks for the headsup! 0.0.34 is also working fine, just in case. Based on the commit history 0.0.35 looked like it could cause issues so I started...

Good to know, I'll keep my eyes open! 🙇🏼

This issue is not stale.

Nope, it's not...