Zack Whipkey
Zack Whipkey
We can close this issue.. I think it was a red herring. Specially if you can't reproduce it.
@ganskef you were right, sorry. also forget the details of this.
We just had the same thing happen to my company, during a prod deploy.
Just ran into this issue myself! thank you for reporting it as it gave me a direction to fix (as the error message was not really helpful).
@stashymane I just discovered the same issue with `paths` recently. You make some good points in general. JSConfig needs to be generated in order to point vscode towards the types...
From my surface level research, it doesn't look like the Metadata dependency API supports this yet. But you might be able to gleam usages by doing the following: - Querying...
I'm running into this issue too, and have a similar setup. I'm working backwards to see if a earlier version works.
aha! I think I figured this out, atleast for my case! @syq7970 Do you have HDR turned on in Windows 11? If so, turn it off, and try the hardware...
weird. started the profiler through the developer tools, disconnected RDP, reconnected, waited couple mins for vscode to unfreeze, and stopped the profiler. Nothing stood out to me as "stuck" or...
@yo1dog That seems to point to an issue with electron or browserview then.