-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow custom node and npm paths #10
Comments
You can specify the path to |
Does not work for me.
|
Could you please retry with Alpha 18? |
Does npm exit with code 0 if you run it as |
@Eugeny Yes it does:
|
Same issue here on Sierra with v1.0.0-alpha.18 ( This definitely appears to be Mac specific. I have Terminus installed on 2 Linux boxes and they pick up npm and allow plugin installation correctly. |
Issue is still present on alpha 21, on OSX. Same with alpha 22. Related to #4 |
Issue is still present with the latest alpha (28). |
I'm having the same issue on alpha 29 using NVM |
Alpha 30, 31 and 32 still have this issue (on macos). |
@compuguy @ClementParis016 do you mean the automatic NPM detection or the |
@Eugeny I was talking about the automatic detection. Though, auto-detection works well on my personal Windows machine with NVM for Windows but it doesn't on my Ubuntu work laptop having NVM. It's may be due to the way they differ on handling the linking of npm & Node executable for the active version. |
@Eugeny Automatic npm detection is broken for me on my Mac. Using npm provided by homebrew. The manual npm config option wasn't working on that either. A Ubuntu machine I use has no problems with automatic npm detection, though. |
Both automatic and manual detection are still broken on Alpha 35 (I'm using nvm) However, it did work once I manually symlinked ** ** terminal:
bell: 'off'
shell: /bin/bash
hotkeys: {}
appearance:
tabsLocation: top
dock: 'off'
frame: full
npm: /home/raghd/programs/nvm/versions/node/v8.4.0/bin/npm |
Same issue with npm installed with brew |
Could you guys please retest this with the latest alpha? I've added some improvements for the node & npm search paths there. Thanks! |
@Eugeny Just tried it, it is no longer showing OS: |
@rhamzeh any idea why the terminal says |
@Eugeny No sorry, it prints that as soon as I click on "Plugins" :/ |
I'm using Windows Subsystem for Linux, and I've used the following value
which seems to work, plugins are listed, Terminus reports that npm is installed, except that when I attempt to install plugins, everything appears to work, no errors, yet after a restart, nothing was installed. There are no error logs either. I noticed when I clicked on the "Plugins Folder" button in the up right corner, that Windows explore said the folder did not exists, so I created, but still nothing is installed. I opened the DevTools, but nothing is logged to the console and no errors appear on the console. using latest Alpha 62 |
Robert, on Windows, Terminus requires a win32 NodeJS build with NPM to install plugins. The reason is that the plugin directory is outside of WSL rootfs and that windows-specific package versions should be installed (as opposed to Linux ones that WSL-based NPM would install). |
That makes sense. Was hoping to not need to install multiple nodejs on the machine. |
Retested with alpha 67, auto npm detection with homebrew installed npm (symlinked at |
Not working for me on alpha 68. |
I have the same issue with macOS Probably when it asks for the PATH environment with the current user shell So, to fix the problem I simply add the export PATH="/usr/local/bin:$PATH" Hope this will be helpful.
|
I'm using Alpha 69 $ echo $PATH
/Users/peter/.asdf/shims:/usr/local/opt/asdf/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/MacGPG2/bin $ ls /Users/peter/.asdf/shims
node npm npx $ npm
Usage: npm <command>
where <command> is one of:
access, adduser, audit, bin, bugs, c, cache, ci, cit,
completion, config, create, ddp, dedupe, deprecate,
dist-tag, docs, doctor, edit, explore, get, help,
help-search, hook, i, init, install, install-test, it, link,
list, ln, login, logout, ls, outdated, owner, pack, ping,
prefix, profile, prune, publish, rb, rebuild, repo, restart,
root, run, run-script, s, se, search, set, shrinkwrap, star,
stars, start, stop, t, team, test, token, tst, un,
uninstall, unpublish, unstar, up, update, v, version, view,
whoami
npm <command> -h quick help on <command>
npm -l display full usage info
npm help <term> search for help on <term>
npm help npm involved overview
Specify configs in the ini-formatted file:
/Users/peter/.npmrc
or on the command line via: npm <command> --key value
Config info can be viewed via: npm help config
npm@6.4.1 /Users/peter/.asdf/installs/nodejs/10.15.0/lib/node_modules/npm I've specficed the path in my
tried this too...
$ ls .asdf/installs/nodejs/10.15.0/lib/node_modules/npm/bin/
node-gyp-bin npm npm-cli.js npm.cmd npx npx-cli.js npx.cmd |
Maybe this has something to do with it? @Eugeny |
@peterlobster it's not a part of any release yet, but you can grab a nightly build |
This would fix the issue of "NPM not installed" for users who install node to a custom folder, or install multiple versions of node using nvm.
The text was updated successfully, but these errors were encountered: