I have this problem with Visual Studio Code for Windows 10: I can't see the NPM scripts in the explorer sidebar.
I deleted all the extensions, uninstalled VS Code, and installed the latest version of VS Code again with no custom options and no extensions, but it didn't solve my problem; the NPM scripts menu does not appear.
How could I fix this so that the NPM Scripts menu option is shown again?
Few places to look for the NPM-Scripts explorer :
The npm-scripts explorer can be enabled or disabled with the below settings, in VSCode's settings.json:
"npm.enableScriptExplorer": false
Default value is false, change to true and it should work. Try restarting VSCode for changes to take effect(although a restart is not often required) if it doesn't show up.
Another very hard to notice place is the three dots ... in the top right corner of your project explorer (verify if NPM scripts is checked). This is something which I had experienced personally for a different extension.
Open "File > Preferences > Settings"
Search "npm script"
Toggle "Npm: Enable Script Explorer"
Close VSCode; reopen
Version 1.59.1
Go to View -> Open View and type: npm scripts:
Appreciate I may be a bit late to answer this question. For me, this was due to npm scripts not being selected to display in explorer. Once I had selected the box, the npm scripts window was available to view.
Hopefully, this has just been fixed - see https://github.com/microsoft/vscode/issues/120279#event-4631666095 and https://github.com/microsoft/vscode/issues/120279#issuecomment-824950294 seeking test verification.
It is in the Insiders now and in Stable early May, 2021. It fixed it for me.
View/Open View...
Type NPM
Click on NPM Scripts
If it still isn't working, see https://github.com/microsoft/vscode/issues/119868
Is your package.json at the root level? Does it make any difference if you open your package.json first, and then check for the view? Or try opening another .json file (or even the Release Notes has been reported as working) and then do a Reload. Otherwise, add your info to the issue.
Work around: If I leave an editor tab open with my package.json (I have one in the root, and in two other places), close and re-open VSC, then it seems to 'find' the NPM View.
TL;DR;
My VSC (1.55.2) is inconsistently showing / not showing the NPM View.
When it starts without the view, I cannot use View->Open "npm".
No option in Explorer options (...)
When it starts with the view, View->Open has a result for "npm".
Has option in Explorer options (...)
Bug report here: https://github.com/microsoft/vscode/issues/120279
Try to delete package-lock.json and restart VSCode.
In my case it worked.
It happens to me sometimes when I open VSCODE.
Whenever it happens I simply load a package.json file.
The NPM SCRIPTS menu still appears when I close the package.json file.
If that doesn't do the trick, try installing NPM-Scripts extension.
If it worked normally before but now it does not, and you have the extension installed and enabled. Then all you have to do is open your package.json file and it will be available again.
I guess this weird behavior happens when you disable all your extensions or may happen if you're installing/removing extensions from a remote container
You can install NPM-Scripts extension which does the same as npm scripts functionality which was build into vscode.
Related
I recently updated python to the latest version 3.10.5 on my Windows 10 desktop using pyenv-win. Everything went fine, except when I launched jupyter lab and found out I can't access the JSON settings editor anymore. I was following the same procedure as always:
Launching jupyterlab from the terminal using the command jupyter lab
Going to the settings menu and choosing Advanced Settings Editor
The settings editor GUI is opened as always and I can change settings through the UI, but I prefer using the JSON settings file.
On the top right of the settings editor there is a button to open the JSON Settings Editor. I click it and nothing happens. This button doesn't do anything. it used to open a text editor with all the JSON settings files. Now it simply does nothing.
I tried reinstalling jupyter lab completly, including removing every custom extension and reseting all setting to the default, and it didn't help. The JSON Settings Editor button still doesn't do anything.
Can anyone explain to me why this happens and how I can fix this?
This is a bug in the latest JupyterLab release v3.4.4. I have reproduced it on 3.4.4 and opened a pull request to fix it: jupyterlab#12892. The fix should be included in the next patch release. In the meantime you can downgrade to 3.4.3 which is not affected.
Thank you for highlighting it (next time if it looks like a bug feel welcome to report directly at https://github.com/jupyterlab/jupyterlab/issues).
Edit: JupyterLab 3.4.5 is now released. Please upgrade using your package manager to get the fix.
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”.
The "NPM Scripts" view is missing from Views dropdown in the Explorer in my VS Code after I updated to version 1.58.0 today.
How do I enable that?
I have tried "Reload Window", restarting VSCode altogether and adding "npm.enableScriptExplorer": true to no avail.
P.S. my angular project is not in top-level directory, but it made no difference before this update.
After adding "npm.enableScriptExplorer": true in the configuration file, you must display it because by default it is hidden!
You can unhide it by using the Views menu in the explorer:
way to resolve issue
ref : https://github.com/microsoft/vscode/issues/104591#issuecomment-673959672
So I made a custom theme for VScode, and I just want to install it for personal use, not to be put on the marketplace. Once I customized it, and edited the package.json and README.md files appropriately, I opened the terminal and ran these lines of code, one after the other. This is my first time making a theme and therefore first time running these commands (in case that matters):
npm i -g vsce
Next:
vsce package
I then saw the .vsix file created in my explorer on the left hand side. The text appears dim, I'm not sure if that is an indication that something is wrong... is it?
I right clicked on the file and selected 'Install Extension VSIX' on the bottom
There was no indication that anything had happened, even after clicking install several times.
After that, I tried finding the theme in the color theme searcher, and couldn't find it there either, leading me to assume that it did not install. I also tried doing it through the terminal, using:
code --install-extension dv1-0.0.1.vsix
However, I was greeted by the response: "zsh: command not found: code". I was following this video tutorial to install my custom theme: https://www.youtube.com/watch?v=QCqWzb-9Sy8
The section about installing your theme starts at 11:05. Is there something I have to download to utilize that 'code' command? Regardless I feel like the first installation method I tried should have worked.
In case this matters, I will mention that a "vsc-extension-quickstart.md" file was created as well. I did not find it helpful.
Any way in which you can help is much appreciated!
UPDATE
I installed the 'code' command, so I ran
code --install-extension dv1-0.0.1.vsix
in my terminal and this time it told me that the current VScode version was incompatible, so I went to my package.json and changed the version to 1.51.1 and I was able to install my theme. However, now when I look for the theme in the theme search, I am not seeing it. I know it was installed because it says so in the terminal.
Any idea where I can find and use my theme? Thanks
Recently I run into problem with ESlint extension in VS code. When I launch VS code and open up a js file, it popup message "Couldn't start client ESlint". It used to work fine. I tried to re-install eslint, VS code but it didn't help. Here are the versions I used.
VS code: 1.44.0 (user setup)
eslint: v6.8.0
ESLint Extension for VS code: 2.1.2
You need to dig a little bit more to get more details.
A good place to start would be to run the eslint show output command in VSCode. That should be a good starting point.
screenshot of ESLint: Show Output Command
The bottom line is that you need to follow the conventional installation path:
add eslint extension in vscode.
install eslint locally or globally via npm,
run eslint init in your project path and select proper configurations.
restart vscode just to make sure the settings are active.
again, the eslint output console should be a good starting point.
For me, it turns out I had the eslint.runtime and eslint.nodePath settings set to the specified node path on my system, but they were prefixed like this:
~/.nvm/versions/node/v14.17.0/bin/node
Using $HOME instead of ~ didn't solve it either.
I ended up having to specify an absolute path:
/home/<myusername>/.nvm/versions/node/v14.17.0/bin/node