Skip to main content

usr bin env node


/usr/bin/env: node: No such file or directory

I installed my Node in "$HOME/Apps/node" and also performed local install ("npm install" things without "-g").
This leads me to the "node"  and "npm" binaries to be in  "$HOME/Apps/node/bin" and the packages binaries to be symlinked from "$HOME/node_modules/.bin".

Adding  "$HOME/Apps/node/bin" and  "$HOME/node_modules/.bin" to the PATH allows me calling "node" or "npm" from a terminal, but when comes the time that my Emacs-GTK needs to call "node" or "npm", I get "/usr/bin/env: node: No such file or directory" dispit ethe fact I already made this:

(add-to-list 'exec-path "/home/mihamina/Apps/node/bin")
(add-to-list 'exec-path "/home/mihamina/node_modules/.bin")
 For information, this is happening when it tries to launch "iph" from Intelephense.
So this basically means that the ".bashrc" file has not been sourced (after all, I did not launch BASH), and Intelephense does not consider the Emacs "exec-path" configuration.

The only solution I made is to append "$HOME/Apps/node/bin" and  "$HOME/node_modules/.bin" at system boot time.

To achieve this, I create the "/etc/profile.d/" and put the following lines in:
append_path '/home/mihamina/Apps/composer/bin'
append_path '/home/mihamina/Apps/symfony/bin'
append_path '/home/mihamina/node_modules/.bin'
append_path '/home/mihamina/Apps/node/bin'

Reboot and enjoy!

Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href=''" parameter. npm run build --base-href=' did not set the base href in indext.html After looking for a while, I found where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='

Jenkins invalid privatekey

Publish over SSH, Message "invalid privatekey:" With quite recent (June-July 2020) installations of Jenkins and OpenSSH, I have the following error message when using the "Deploy overs SSH" Jenkins plug-in and publishing artifacts to the target overs SSH: jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message [invalid privatekey: [B@d8d395a] This problem seems to be referenced here: Just regenerate a key with the right parameters To solve it: ssh-keygen -t rsa -b 4096 Or ssh-keygen -t rsa -b 4096 -m PEM

Emacs TypeScript Development

Emacs Configuration for Typescript In order to comfortably develop on Node, React or Angular projects with Emacs, TIDE is a good solution. We have TypeScript code highlight (that is the minimum!) and code completion based on the codebase (not only on locally defined and builtins) In order to achieve that: Install Emacs (24+) Install Node Install Typescript (which will provide "tsserver") Install TIDE and some usefull dependencies Configure Emacs to use all those Node is then installed in " /home/mihamina/Apps/node-v12.18.0-linux-x64/bin ": you should add it to your PATH. Installing Typescript is done with: npm install --save typescript @types/browserify After that, "tsserver" will be in " /home/mihamina/node_modules/.bin " Then comes the installation of TIDE: With the Emacs package manager, M-x package-install , install "tide". Do the same for "web-mode", "flycheck", "company" "js2-mode" and "