See the below error and jsconfig.json file contents:
I have no idea what the problem is... The "source-map" file the error is referring to DOES exist at the given path.
Note, that everything works fine and as expected, so the error does not seem to cause any problems.
Any help or suggestions are greatly appreciated.
Thanks!
Run the Developer: Reload Window command in VSCode, or close & re-open VSCode. That solved it for me.
Related
I am trying to debug in vscode, but faced one problem which is the debug programs I previously set in launch.json doesn't appear.
I also found that the vscode shows debug programs from launch.json (the toppest folder, not subfolder)... Does anyone know how to solve it? Thanks in advance..
I apologize if this question has been answered somewhere else, but so far I am unable to locate it if it was.
Background:
As many folks have suffered the dreaded blank screen on VS Code, I deployed the recommended fix for --disable-gpu. This fix worked just fine for me and I have been using it ever since.
Issue:
Since this fix has been deployed, I'm unable to view the details page when viewing an Extension. The page/tab just shows up as blank. This happens with any extension, regardless of if I've installed it or not. This in and of itself is not a deal breaker for me, but I was hoping to use the Jupyter Notebook extension, but this seems to be impacting this as well.
If anyone has any guidance, please let me know.
Screenshot showing lack of details
I was able to get this corrected by creating a .bat file that I use to open VS Code. The code file was set up like the following:
cd C:\Program Files\Microsoft VS Code\
Code.exe --disable-software-rasterizer --disable-gpu --no-sandbox
Not sure how this problem specifically occurred. I've been doing some googling trying to narrow down what exactly is going wrong as my project was fine a few days ago. When i attempt to debug my VSCODE project i'm presented with this error.
this is a picture of my launch.json file:
Also, this an error if it helps displayed in the debug console.
Things i've tried so far,
Rebooting the computer
Uninstalling and Reinstalling VSCODE as well as disabling extensions
Creating a new VSCODE Project to attempt to debug
Deleting the launch.json file and creating a new one
just delete the launch.json file and it will work again
After spending some time debugging I solved this problem by simply installing npm packages, I executed command npm i
Just make sure that your npm packages are all installed and none is failing.
Hopefully this helps you or someone with the same issue.
I've solve this problem.
Remove the launch.json file and do not replace it.
Just try to build with F5 button.
Start Debugging from within VSCode
run npm start from a separate terminal and wait for the server to start
refresh the page in your browser
My intuition is that this would create 2 instances of the server binding to the same port and cause a bunch of problems. I'm not sure why, but in my case it worked as expected and let me debug with breakpoints normally.
You don’t need to use the VS Code run button with Live Server. You just right-click the HTML file in explorer and use the menu option “Open with Live Server”.
I tried to uninstall VSCode, cleaned up all data files, uninstalled all the extensions. None of them was working for me. please help!!!
i encountered same problem, make new workspace folder and it will solve the issue
Open workspace/folder and select the file from vscode explorer, don't open the file directly.
Type in Command palette of VS Code "Enable Error Squiggles".. This worked for me!!
Go to the settings and type Error Lens: Enabled.
Make sure you check the box.
I have used the live sass compiler a few hours back, it worked fine, but now it's not working. Can you please let me know what can be the problem?
This is what I see when I hit ctrl + s
This is my project folder structure
This is settings in settings.json
Thanks for your help in advance.
Do you have any other folders open at the same time in Visual Studio? This happened to me one day and by closing all the folders started working again. It doesn't work by just restarting Visual Studio, you have to close them by hand.
The settings.json seems alright and the compiler isn't showing any errors.