Node.js 0.12.0 on CentOS 6 (by rpm) - node.js

Im interested on installing the 0.12.0 version of Node.js on a CentOS 6 machine. I have noticed however that through yum, the latest version available is 0.10.33.
Given my environment I can ONLY install packages through RPM, and as I might be inclined to generate my own rpm of Node.js 0.12.0, I would like to know if there is any specific reason why the latest version has yet been made available. Are there by any chance some known problems when running the latest version of Node.js on CentOS 6? Or are there any stable 0.12.0 rpm packages out there I might have missed?
Thanks in advance!

Apparently there is no problem:
https://groups.google.com/forum/#!topic/nodejs/tqiKHCqpeuM
Node v0.12.0 should be stable on all versions os Centos back to 5.7

Related

How to install riscv-tools older version using Homebrew

I need to use riscv64-unknown-elf-gdb with Clion (on Mac) that is currently supporting only up to version 9.2, I have installed riscv-tools using brew install riscv-tools as instructed here and got the latest version which is 10.1.
After that, I tried brew install riscv-tools#9.2.0 but got: No available formula or cask with the name "riscv-tools#9.2.0"
Is there any way to install a specific older version?
And how bad it is to use an usupported version of gdb with Clion? so far it seems to be working anyway.
A solution in Linux will also be very appreciated.
If you want to get gdb 9.2, you can easily get it from https://ftp.gnu.org/gnu/gdb/ where gdb 9.2 already support risc-v.

brew upgrade node failing with error Error: node not installed , even when I do have old version of node installed

Mac OS 10.13.6 with homebrew installed, today had to upgrade it because of new homebrew policy
Can't update or upgrade Homebrew
after doing this, tried upgrading node to latest version and got below error
Warning: You are using macOS 10.13.
We (and Apple) do not provide support for this old version.
You will encounter build failures with some formulae.
Please create pull requests instead of asking for help on Homebrew's GitHub,
Twitter or any other official channels. You are responsible for resolving
any issues you experience while you are running this
old version.
Error: node not installed
In fact I do have old version of node installed
node -v
v12.0.0
how to solve this weird problem ?
Note:
Few weeks back I did below to use older version of node
Install NVM On Mac With Brew
I'm really confused atm, who is managing node on MAC ? Is it NVM / homebrew ?

Linuxbrew doesn't see the latest version of node.js

I'm trying to install node.js on Ubuntu using linuxbrew. I'm running the following commands:
brew update
brew info node
the output is
node: stable 6.0.0, HEAD
However version 6.1.0 should already be available (you could verify it in e.g braumeister)
Any ideas what could be the issue here?
Linuxbrew is built on top of Homebrew and updates to the latter need to be manually ported to the former, which is why you can expect a small update lag. Braumeister and similar websites get their infos from Homebrew.

Why does AWS Lambda uses older node version?

It seems like aws lambda uses older node version 0.10.36
Is there any reason to not to use newer versions of node or maybe even latest iojs compiler?
Thanks
A simple answer is that 0.10.36 is the version you get from the EL6 EPEL repository with yum install nodejs. You have to do extra work to get a newer version.

Node.js version not correct?

I just downloaded node.js via their website and found that the version I had on my local machine was way outdated (v5.11pre). So, seeing that there was a 10.2 version out, I decided to completely uninstall node.js from my machine and reinstall the latest and greatest version!
After going through the steps to install everything I ran the following command and found out something strange:
$ node --version
v0.5.11-pre
Can someone explain why the tarball for node 10.2 just installed a extremely old version of node? Also, how can I get the newest version!?
EDIT:
If it helps, I'm using Ubuntu 12.04.
I guess that the correct version was installed indeed, but your path still points to the old installation.

Resources