You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bugIssue identified by VS Code Team member as probable bugcandidateIssue identified as probable candidate for fixing in the next releaseverifiedVerification succeededwindowsVS Code on Windows issues
When I open a .js or .ts file, if I try running TypeScript: Open TS Server Log from the command palette, nothing happens.
Upon further inspection, if I check my server trace, the log file seems to not exist at all - however, the actual directory structure is still present.
I seem to have no issues with VS Code stable, or VS Code on the web.
mjbvz
added
bug
Issue identified by VS Code Team member as probable bug
candidate
Issue identified as probable candidate for fixing in the next release
labels
Feb 27, 2023
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugIssue identified by VS Code Team member as probable bugcandidateIssue identified as probable candidate for fixing in the next releaseverifiedVerification succeededwindowsVS Code on Windows issues
Version: 1.76.0-insider (user setup)
Commit: 7b6b686
Date: 2023-02-22T05:24:32.270Z
Electron: 19.1.10
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: 10.2.154.26-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: Yes
When I open a
.js
or.ts
file, if I try runningTypeScript: Open TS Server Log
from the command palette, nothing happens.Upon further inspection, if I check my server trace, the log file seems to not exist at all - however, the actual directory structure is still present.
I seem to have no issues with VS Code stable, or VS Code on the web.
(CC @mjbvz)
The text was updated successfully, but these errors were encountered: