I want to remove node to install it with nvm but I can't uninstall it.
I installed node twice, once I installed it wrong and the second time I did it right, I uninstalled one of the two nodes but the second time I don't know where it is and because of that I can't uninstall it.
I already try:
brew uninstall --force node
look tutorial how to uninstall node js from mac M1
Does anyone know how to find node location on mac M1 ?
It is dependent by your packet manager.
For example, asdf version manager show info like that:
asdf info nodejs
OS:
Linux slonzal 5.19.0-26-generic #27-Ubuntu SMP PREEMPT_DYNAMIC Wed Nov 23 20:44:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
SHELL:
zsh 5.9 (x86_64-ubuntu-linux-gnu)
ASDF VERSION:
v0.10.2-7e7a1fa
ASDF ENVIRONMENT VARIABLES:
ASDF_DIR=/home/slon/.asdf
ASDF INSTALLED PLUGINS:
nodejs https://github.com/asdf-vm/asdf-nodejs.git
yarn https://github.com/twuni/asdf-yarn.git main 376c540
Other version managers have own syntax. Try to npm -h, if you use npm.
Related
For new Apple M1 silicon mac-books, how can we install node on processor x86_64 arch.
According to node.js download page, they don't provide the mac installer for x86_64 processors. Please refer the download page - https://nodejs.org/en/download.
Note: Node Mac Installer only support ARM64 processor.
I have tried Rosetta terminal options, but not able to install node#16 with x86_64 arch on M1 mac machine. Please provide any suggestions to solve this problem.
You can do brew install node#16, but it requires some PATH environment variable hacks.
I'd recommend nvm or asdf plus nodejs plugin
My goal is to install node version 8 so I can run Gulp on a project.
I'm working on an old project that has been neglected and passed downed to me by another developer. I'm told I can work with Gulp by installing Node Version 8 and declaring the node version in my package.json file.
But whenever I try to run nvm install 8I receive the error error: "unsupported ARM architecture"
My system is MacOS Big Sur M1 Chip
I am not too sure what I'm supposed to do here. Please help!
Solution
The solution was to change the architecture of my shell from arm64 to x86.
Macs with M1 chip
January 2021: there are no pre-compiled NodeJS binaries for versions prior to 15.x for Apple's new M1 chip (arm64 architecture).
Some issues you may encounter:
using nvm to install, say, v14.15.4:
the C code compiles successfully
but crashes with an out of memory error when used
increasing the memory available to node still produces the out of memory errors: $ NODE_OPTIONS="--max-old-space-size=4096" ./node_modules/.bin/your_node_package
when using nvm to install some versions, the compilation fails
One solution to this issue is to change the architecture of your shell from arm64 to x86.
Let's assume that:
you already have versions 12.20.1 and 14.15.4 installed using nvm
the current version in use is 14.15.4
you are using the zsh shell
you have Rosetta 2 installed (macOS prompts you to install Rosetta 2 the first time you open a Intel-only non-command-line application, or you may install Rosetta 2 from the command line with softwareupdate --install-rosetta)
//# Check what version you're running:
$ node --version
v14.15.4
//# Check architecture of the `node` binary:
$ node -p process.arch
arm64
//# This confirms that the arch is for the M1 chip, which is causing the problems.
//# So we need to uninstall it.
//# We can't uninstall the version we are currently using, so switch to another version:
$ nvm install v12.20.1
//# Now uninstall the version we want to replace:
$ nvm uninstall v14.15.4
//# Launch a new zsh process under the 64-bit X86 architecture:
$ arch -x86_64 zsh
//# Install node using nvm. This should download the precompiled x64 binary:
$ nvm install v14.15.4
//# Now check that the architecture is correct:
$ node -p process.arch
x64
//# It is now safe to return to the arm64 zsh process:
$ exit
//# We're back to a native shell:
$ arch
arm64
//# And the new version is now available to use:
$ nvm use v14.15.4
Now using node v14.15.4 (npm v6.14.10)
source: https://github.com/nvm-sh/nvm
Find UR iTerm (or any other termial ur using)
Double-click =>【get info】
In General Panel：
✅ Open using Rosetta （selected this item）
Back to termial and continue use nvm install 8
I followed the following steps on a fresh installation of Ubuntu 20.10:
# Clone this repository
git clone https://github.com/electron/electron-quick-start
# Go into the repository
cd electron-quick-start
# Install dependencies
npm install
# Run the app
npm start
The output fromm the start command is:
up to date, audited 89 packages in 1s
found 0 vulnerabilities
> electron-quick-start#1.0.0 start
> electron .
(node:4081) electron: The default of contextIsolation is deprecated and will be changing from false to true in a future release of Electron. See https://github.com/electron/electron/issues/23506 for more information
The resulting window looks like this:
System Information:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.10
Release: 20.10
Codename: groovy
Linux andy-Parallels-Virtual-Platform 5.8.0-31-generic #33-Ubuntu SMP Mon Nov 23 18:44:54 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Node version: v15.3.0
Electron-quick-start commit hash: 2b0dbb098
After doing a Google Image search I found the cause and the current resolution:
https://github.com/electron/electron/issues/26061
This only happens on Parallels at a specific version.
in QNAP APP center has node.js 4.x and 0.8.X version
However, these two versions are too old, I hope we can install a newer version.
I try to login linux system installed through the command
https://www.ostechnix.com/install-node-js-linux/
nas seems to have removed some of the command, I checked it is Ubuntu but no apt-get, I can not install node.js through these comman
cat /proc/version
Linux version 3.4.6 (root#BuildServer36) (gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Thu Oct 26 11:01:49 CST 2017
like this
sudo apt-get install nodejs npm
-sh: sudo: command not found
apt-get install nodejs npm
apt-get: command not found
I have not tried to install the mongodb should have a similar problem
My nas model is TS-439 Pro ii
Or just go to qnapclub.eu a repository of “unofficial apps” - download it and install through the GUI in app center...
You have to select accept third party apps and you should be good to go..
I was straggling with the same issue on mine QNAP.
I found this tutorial: https://techblog.dorogin.com/running-nodejs-app-on-qnap-nas-via-pm2-3bdb838524e4 written by Sergei Dorogin.
Highly recommend you to install pm2 which is production manager for node.js
https://github.com/Unitech/pm2
It took me around 3hours to set up everything, because I'm not good with Linux
I haven't played with this yet, but it seems like using Container Station to install an official Node.js Docker image is the way to go. This gives you a complete preconfigured Linux environment to run Node in.
on my mac, key node -v, I get "v6.2.2", on centos, I get "v0.10.36", on centos, I keys "uname -a", I get "Linux VM_80_24_centos 3.10.0-123.el7.x86_64 #1 SMP Mon Jun 30 12:09:22 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux", how can I understand the difference between two version num.
It seems like one is node version and another is npm version. You might executed the different commands.
To check node version:
node -v
will give 'v6.2.2'.
To check npm version:
npm -v
will give 'v0.10.36'.