How do you get past the Windows Script Host error when trying to call `nvm use 16.19.0` - node.js

I need to set the node version to an older version for a new project I am working on. I am on Windows 11 Pro. This is a new computer that I setup yesterday and is pretty clean from a node perspective.
I have just removed nodejs and installed nvm (v 1.1.10).
After calling nvm install 16.19.0, I tried to call nvm use 16.19.0 and recieved the following error popup:
Here is the CLI history:
I was expecting this to set my current node version to 16.19.0.

I was trying to do this while running git-bash from Visual Studio Code so when I loaded up git-bash as Administrator I was able to get the nvm use call to work correctly.
Sorry for the stupid question, but I didn't see it answered on here anywhere else, so hopefully it will be useful to someone else.

Related

In the linked question, what does the op talk about regarding installing node.js in the working directory?

I am a complete newbie to all this.
I tried to install node.js 4 times and then again uninstalled it every time trying different things, thinking one of them would work.
The link to the question is-Cannot find runtime 'node' on PATH - Visual Studio Code and Node.js
After I typed $node --version in powershell terminal in VSCode (after installing node.js in C drive, defaulting to all recommended options in the setup) I get an error. I have uploaded the image of the error.
the error
Please tell me how to get node.js working with VSCode.
To get the version of Node, just type node --version in the terminal without the "$".

What versions of Angular 2 and Angular-cli worktogether on windows vista?

would anybody happen to know the latest versions that work together on Windows Vista? I've been back and forth trying to get the right combination together but ng new never works for some reason or another.
(this is the older post showing what I already tried)
I'm having a bit of a problem here. I attempted to update angular/cli and I got errors telling me I need to update my version of node. I have windows vista so I'm pretty much stuck with node 5.7 and npm 3.6 until I can afford a new computer.
I tried uninstalling angular and clearing the cache and installing angular-cli#1.0.0-beta.14 and it installs. I can create a new project with it though it takes a long time to create it, and it also throws an error with node-pre-gyp. I came across an article on Github that said it's meant to be installed locally in the project and not globally. So I tried uninstalling, clearing cache and installing without -g to make it local within my project folder and it still has errors installing and I still can't serve my project.
How can I clear this all up and just start back with a clean slate of Angular2? I've looked around and everything I find leads me to the docs which are now updated to something beyond what my computer can handle.
I have windows vista so I'm pretty much stuck with node 5.7 and npm 3.6 until I can afford a new computer.
Have you considered running Linux? There are many versions with a lightweight GUI that runs well on older hardware. Ubuntu Mate is an example. It's harder to run node on Windows because of symlinks.

VS Code, change NodeJS version for debugger

I want to change NodeJS version from 4.5.0 to 7.7.2 for VS Code specifically for different projects.
I am using nvm on Mac, and I have two versions stated above. They are for different projects.
Even though I can change from terminal with nvm, VS Code uses default version. I need to change the default version every time and completely restart the VSCode.
Is there a way to alter configuration so it picks up the version I wanted
both for in-app terminal and for running project?
After VS Code 1.21, there is a better solution than the original answer.
You can set "runtimeVersion": "7.7.2" and if you have nvm/nvs installed, it will be able to find that version of Node. Details: https://code.visualstudio.com/updates/v1_21#_node-debugging
--- Original answer ---
In your launch config, you can set a path to a Node executable from nvm like this: "runtimeExecutable": "/Users/me/.nvm/versions/node/v7.7.1/bin/node"

Odoo Mac OSX installation get error "Could not execute command lessc" in PyCharm Community Edition

I installed Odoo 9 on Mac OSX using Homebrew virtual environment.
I installed npm, less and less-plugin-clean-css.
Finally if I launch Odoo from the Mac Terminal, using the appropriate parameters, everything goes well and I can enter my odoo with localhost:8069.
I then setup PyCharm Community Edition for odoo development, but when I run odoo from within PyCharm I get the error:
"Could not execute command lessc"
and obviously the web layout is totally wrong.
I saw here NodeJS plugin in IntelliJ Community Edition does not work that you cannot use NodeJS plugin with PyCharm CE.
My question then is: "How to enable PyCharm CE to use less and get rid of the error?".
If you are in Pycharm in getting error Could not execute command lessc and you have installed less which you can check by entering lessc command in terminal
Fix:
If you are using virtualenv then activate virtualenv from terminal and restart the server again from terminal, this time it won't give any error.
If you are not using virutalenv then you can just run from terminal server without any problems
I'm not sure why this problem is specific to PyCharm.
I had the same issue from PyCharm Professional, but I solve this issue with this way
When i finish installing the PyCharm pro ,then i set the environment variables in the 'run/debug configuraition'
(/usr/loca/bin)
which value(path) i found is using command "which lessc" in the terminal
Then I think the PyCharm can find lessc, and finnally I get rid of this nightmare
`Could not execute command 'lessc'
For me, updating the node was the solution. It was version 0.10.33. Now it's 6.1.12.
Check out this answer. You must uninstall node and reinstall it in a certain order:
https://stackoverflow.com/a/36395799?noredirect=1
At least that is what worked for me.

How to install/use Meteor with Babun Windows Shell

so I have a problem here with this custom cmd shell for windows called Babun and using it with meteor. To be honest, I am still a beginner when it comes to the cmd etc... but here is the situation.
So I am working on a meteor website and I am using WebStorm for this, meteor is already installed on my computer and the meteor commands are recognized on the windows cmd. I don't really like the default look of the windows cmd and add to the fact that I have to force it into legacy code mode in order for it to properly work as a terminal for WebStorm. That's why I searched for a more 'feature - rich' cmd and came across Babun which seems pretty handy.
I got as far as getting Babun to work within WebStorm without any problems, but its not recognizing meteor at all like my default windows cmd. This is the error I keep receiving from the console: zsh: command not found: meteor
Which is funny because my default windows cmd can pick it up, why can't Babun or this "oh-my-zsh".
I already tried adding the meteor plugin as instructed here: https://github.com/robbyrussell/oh-my-zsh/wiki/Plugins but meteor is still not being recognized for me. I'm running windows 10 if that helps with the latest versions of both Meteor JS and WebStorm.
If anyone could shed some light into this issue I'm having that would be greatly appreciated!
Did you add the path in the .zshrc file? See how to add path in cygwin. A lot of Babun issue can be resolved by using cygwin solution.
You can confirm by running: which meteor

Resources