nodejs in Linux (CentOS): compilation and installation from source

Third party dependency libs

sudo yum groupinstall "Development Tools"

Note: Development Tools contains various 3rd party libs to compile and build new rpm from the source.

If above command does not install any lib in your machine, then you may try the following command, (In my machine, Development Tools did not install anything).

sudo yum groupinstall "Additional Development"

Compilation and installation steps

Download the nodejs from the official site: https://nodejs.org/en/download/

1) Create node-4.1.2 installation directory in the /opt with proper read/write/executable permission
     i.e: /opt/node-4.1.2

2) Run the following commands in the downloaded source folder of node:

     2.1) sudo ./configure --prefix=/opt/nodejs-4.1.2
     2.2) sudo make install

 Note: 

You may want to add more option during configuring process. To see more options: 
     ./configure --help

 In my case, I kept default settings. I just configured my desired installation directory.

You may want to install nodejs in different directory. In this case, you have to change --prefix value to your desire nodejs installation directory path instead of /opt/nodejs-4.1.2.

3) Create node_home.sh file in /etc/profile.d folder:

      #NODE_HOME
      export NODE_HOME="/opt/nodejs-4.1.2"
      export PATH=$NODE_HOME/bin:$PATH

 4) Logged out or restart the machine
 
5) Update npm: npm install -g npm. (Depending on permission, you may need to use sudo/su command)

Yes! your are done. nodejs is installed successfully with updated npm (if update available).

Comments

Post a Comment

Popular posts from this blog

There is a process already using the admin port 4848 -- it probably is another instance of a GlassFish server; ERROR

After long time later, I am writing my programming blog again. Today, I downloaded glassfish-3.1.2.2-unix.sh. I am running Fedora 16. After successful installation of the glassfish, I was getting error when I ran the the following command: asadmin>start-domain "There is a process already using the admin port 4848 -- it probably is another instance of a GlassFish server. Command start-domain failed." Then I checked my hostname of the machine: hostname I got my hostname is nix-domain Now, nix-domain is not listed in the /etc/hosts file. Therefore, I added nix-domain in the file. 127.0.0.1               localhost nix-domain Now, I tried to run the start-domain again. It started perfectly without any error. Therefore, I understood that my machine assigned hostname 'nix-domain' is not listed in the hosts file, glassfish generated the error. I am hoping, it is not only the solution, there must be...
Read more

How to install Homebrew in Mac OSX (High Sierra)

Homebrew setup guide This guide describes how to install Homebrew and few ferequently used Homebrew commands. Using Homebrew you can install software very easily. It is like linux "yum" command. Install Homebrew (The missing package manager for OS X): $/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" $brew doctor   (You should see "Your system is ready to brew." on the console output. Do not move forward unless you see this.) Common commands: Check version of brew:    $brew --version Search Homebrew repo: $brew search %app name% (i.e: I want to check "wget" is available or not. $brew search wget) Check app information:    $brew info %app name% (i.e: $brew info wget) Install software package: $brew install %app name% (brew install tree) Uninstall software package: $brew uninstall %app name% (brew uninstall tree) Check installed packages in your system: $brew list Ins...
Read more

WildFly 19 and Log4J2

In this post, I would like to share my story about external configuration file of Log4J2. I developed a Java web application in WildFly 19 application server. It was my pet project. I followed few strict rules about 3rd party libraries. For example, I did not use log4j2-web library/jar file. It was the challenge because in some workplace you cannot have luxury to get all bells and whistle. You have to accept the situation. Therefore, I took this challenge to use external configuration file of Log4J2 in the web application without depending on log4j2-web jar file. My development environment's logging configuration is not same as production environment. In this case, I do not want to swap between development configuration and production configuration file during deployment.    The above situation can be mitigate by two ways: Use external logging configuration file. User application server specific logging system. For exampke, ...
Read more