NPM is refusing to acknowledge all commands currently

Question

NPM is refusing to acknowledge all commands currently

When I try to run the command below:

npm install nodemon -g

The output shows:

/home/ubuntu/.node/bin/nodemon -> /home/ubuntu/.node/lib/node_modules/nodemon/bin/nodemon.js
<a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="d7b9b8b3b2bab8b997e6f9e5f9e6">[email protected]</a> /home/ubuntu/.node/lib/node_modules/nodemon
├── <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="a3cecacdcacec2d7c0cbe3938d908d93">[email protected]</a> (<a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="512238363c243f3511607f617f61">[email protected]</a>, <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="a9c5dbdc84cac8cac1cce99b879c8799">[email protected]</a>)
├── <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="7a0a09570e081f1f3a4a544a5449">[email protected]</a> (<a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="b2d7c4d7dcc69fc1c6c0d7d3dff2829c879c81">[email protected]</a>)
└── <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="94e1e4f0f5e0f1b9fafbe0fdf2fdf1e6d4a4baa5baa5a4">[email protected]</a> (<a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="394a5c544f5c4b790b170a170b">[email protected]</a>, <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="accfc4cdc0c7ec9c8298829c">[email protected]</a>, <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="b9dad6d7dfd0decacdd6cbdcf989978a9788">[email protected]</a>, <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="2e5c4b5f5b4b5d5a6e1c001a17001e">[email protected]</a>)

However, after installing any node package like forever as shown below:

npm install forever -g

I encounter an issue accessing the newly installed commands such as nodemon where it says:

nodemon: command not found

Strangely, I can run them if referencing the file directly like this with forever:

/home/ubuntu/.node/lib/node_modules/forever/bin/forever server/app.js &

This works just fine. Any idea why? How can I fix this issue?

Looking at my profile...

  GNU nano 2.2.6                            File: /home/ubuntu/.profile                                                               

# ~/.profile: executed by the command interpreter for login shells.
# This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login
# exists.
# see /usr/share/doc/bash/examples/startup-files for examples.
# the files are located in the bash-doc package.

# the default umask is set in /etc/profile; for setting the umask
# for ssh logins, install and configure the libpam-umask package.
#umask 022

# if running bash
if [ -n "$BASH_VERSION" ]; then
    # include .bashrc if it exists
    if [ -f "$HOME/.bashrc" ]; then
        . "$HOME/.bashrc"
    fi
fi

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
    PATH="$HOME/bin:$PATH"
    export PATH = /home/ubuntu/.node/bin:$PATH

fi

Command outputs! :

echo $PATH:
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games

And when running ls -la:

ls -la
drwxrwxr-x 2 ubuntu ubuntu 4096 Dec  6 14:42 .
drwxrwxr-x 4 ubuntu ubuntu 4096 Dec  6 12:24 ..
lrwxrwxrwx 1 ubuntu ubuntu   39 Dec  6 14:42 forever -> ../lib/node_modules/forever/bin/forever
lrwxrwxrwx 1 ubuntu ubuntu   42 Dec  6 14:19 nodemon -> ../lib/node_modules/nodemon/bin/nodemon.js

Suddenly, upon restart, I get these error messages:

-bash: export: `=': not a valid identifier
-bash: export: `/home/ubuntu/.node/bin:/home/ubuntu/.node/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games': not a valid identifier

node.js npm

Answer 1

Answer №1

Looks like your Node.js installation is acting up

Here are the steps to install Node.js from source on OSX or Linux:

NOTE - This method installs both node and npm together in a single release.

To start fresh, remove any prior installations of node and npm along with the following:

sudo mv ~/.npmrc ~/.npmrc_ignore
sudo mv ~/.npm   ~/.npm_ignore
sudo mv ~/tmp    ~/tmp_ignore
sudo mv ~/.npm-init.js ~/.npm-init.js_ignore

Download the source code from: https://nodejs.org/en/download/stable/
or select a specific release from https://nodejs.org/download/release

Once downloaded, navigate into the directory containing the source code

cd node-v5.5.0  # or whatever current version is

It is recommended to run the following commands as yourself and not as root (sudo)

Choose one of the following NODE_PARENT locations to specify where Node will be installed:

export NODE_PARENT=/some/desired/install/path_here
export NODE_PARENT=/usr/local/bin/nodejs   # Use only if necessary to install as root
export NODE_PARENT=${HOME}/nodejs-v0.10.33 # Recommended choice

export PATH=${NODE_PARENT}/bin:${PATH}      # Ensure executables can be found
export NODE_PATH=${NODE_PARENT}/lib/node_modules # Set location for Node modules 

./configure   --prefix=${NODE_PARENT}

make
make install

This will install Node.js in the directory specified by --prefix

When using syntax: npm install -g some_cool_module the -g flag installs globally in $NODE_PATH rather than in the current directory

IMPORTANT - Add the three export xxx=yyy commands mentioned above to your ~/.bashrc or similar file to persist these environment changes

Answer 2

Looks like your Node.js installation is acting up

Here are the steps to install Node.js from source on OSX or Linux:

NOTE - This method installs both node and npm together in a single release.

To start fresh, remove any prior installations of node and npm along with the following:

sudo mv ~/.npmrc ~/.npmrc_ignore
sudo mv ~/.npm   ~/.npm_ignore
sudo mv ~/tmp    ~/tmp_ignore
sudo mv ~/.npm-init.js ~/.npm-init.js_ignore

Download the source code from: https://nodejs.org/en/download/stable/
or select a specific release from https://nodejs.org/download/release

Once downloaded, navigate into the directory containing the source code

cd node-v5.5.0  # or whatever current version is

It is recommended to run the following commands as yourself and not as root (sudo)

Choose one of the following NODE_PARENT locations to specify where Node will be installed:

export NODE_PARENT=/some/desired/install/path_here
export NODE_PARENT=/usr/local/bin/nodejs   # Use only if necessary to install as root
export NODE_PARENT=${HOME}/nodejs-v0.10.33 # Recommended choice

export PATH=${NODE_PARENT}/bin:${PATH}      # Ensure executables can be found
export NODE_PATH=${NODE_PARENT}/lib/node_modules # Set location for Node modules 

./configure   --prefix=${NODE_PARENT}

make
make install

This will install Node.js in the directory specified by --prefix

When using syntax: npm install -g some_cool_module the -g flag installs globally in $NODE_PATH rather than in the current directory

IMPORTANT - Add the three export xxx=yyy commands mentioned above to your ~/.bashrc or similar file to persist these environment changes

Answer 3

Answer №2

Make sure to include /home/ubuntu/.node/bin in your PATH environment variable.

For example, in either your .profile or .bashrc file, add the following line:

export PATH = /home/ubuntu/.node/bin:$PATH

* UPDATE *

It is recommended not to place the updated path within the if statement, as these are separate concerns (the existence of a home bin and configuring the node module path).

Additionally, do not forget to reload your .profile after making changes:

source /home/ubuntu/.profile

Answer 4

Make sure to include /home/ubuntu/.node/bin in your PATH environment variable.

For example, in either your .profile or .bashrc file, add the following line:

export PATH = /home/ubuntu/.node/bin:$PATH

* UPDATE *

It is recommended not to place the updated path within the if statement, as these are separate concerns (the existence of a home bin and configuring the node module path).

Additionally, do not forget to reload your .profile after making changes:

source /home/ubuntu/.profile

NPM is refusing to acknowledge all commands currently

Answer №1

Answer №2

Similar questions

Having trouble resolving '___' from the 'home' state? Dealing with an angular ui-router complication?

What is the best way to organize an Express application that handles both API requests and views?

The procedure for deleting npm and node package on a Mac system

Is it necessary to utilize ngrok to expose both front and back ends in a MERN stack in order for CRUD operations to function properly?

Issue: The --outFile flag only supports 'amd' and 'system' modules

Error: Callback function in Mongoose Populate is returning undefined

Is it feasible to utilize Google Calendar API for JavaScript through npm install? Alternatively, can the Google Calendar API be utilized for Node.js in the browser within Next.js?

How can I sync changes between two variables in node.js?

"Every time I try to use passport-jwt in my Node.js application,

Move the dist folder to the libs directory using webpack

IDE cannot find imported modules even though the NPM Package is functioning correctly

Protecting my HTTP connections

Is there a way to send URL variables to express.js similar to how it's done in PHP?

What reasons underlie the existence of various methods for importing Modules in JavaScript?

In Sequelize, the "afterBulkCreate" hook consistently provides the most recent values in the _previousDataValues, particularly when utilizing updateOnDuplicate to modify specific columns

Encountering a Troubleshooting Issue with ArcGIS JS API 4.7 and N

The anchor tag fails to trigger the onClick function in React

The command line utility for webpack encountered an unfamiliar argument: --output

Twilio's phone calls are programmed to end after just 2 minutes

403 Forbidden - PUT https://registry.npmjs.org/shah - Access Denied: You are not authorized to release the package "shah". Please ensure you are logged in with the appropriate credentials