Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
VS Code extension won't start - Cannot read property 'message' of undefined
See original GitHub issueDescribe the bug
The VS Code extension won’t start. If I look in the dev tools, this is what I see:
Please complete the following:
Which version of .NET Interactive are you using? There are a few ways to find this out:
- In a notebook, run the
#!aboutmagic command. - At the command line, run
dotnet interactive --version.
From VS Code:
Installing .NET Interactive version 1.0.160204…
- VS Code: 1.52-insiders
- .NET Interactive extension: v1.0.160204
- .NET Install Tool extension: v1.0.0
- OS
- Windows 10
- macOS
- Linux (Please specify distro)
- iOS
- Android
- Browser
- Chrome
- Edge
- Firefox
- Safari
- Frontend
- Jupyter Notebook
- Jupyter Lab
- nteract
- Visual Studio Code
- Other (please specify)
Screenshots
If applicable, add screenshots to help explain your problem.
Issue Analytics
- State:
- Created 3 years ago
- Comments:12 (7 by maintainers)
Top Results From Across the Web
VSCODE: Cannot read property 'local' of undefined
It is most probably because Code doesn't have privilege to write to the extension folder, which is by default ~/.vscode/extension.
Read more >Error while Authorizing an ORG using VS Code Cannot ...
Try going to the .sfdx folder under Users/[name]/.sfdx and delete everything in there. I had the same problem and this fixed it.
Read more >Cannot read properties of undefined (reading 'uri') : r/vscode
Error is: This issue only occurs when I don't have a folder in the workspace. What should I do?
Read more >VS Code API | Visual Studio Code Extension API
VS Code API is a set of JavaScript APIs that you can invoke in your Visual Studio Code extension. This page lists all...
Read more >How To Fix the "uncaught typeerror: cannot read property ...
The “uncaught typeerror: cannot read property” error mainly occurs when you try to use or access an undefined variable.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I am having this issue as well, both when trying to open an existing notebook and when trying to open a new one. I’m on Windows 10 in Visual Studio Code with .NET Interactive Notebooks v1.0.160901.
I haven’t been able to reproduce this issue recently. If anyone can, please reopen it and comment here with what version of the extension you’re using.
Thanks.