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
NVM + other bin commands undetected #144
Comments
It looks like the special prerun xxh plugin is needed to support these tools. |
Attempting to achieve this and xxh considers my package as an unknown package type when installing from Github and as a local path: xxh +I https://github.com/cyrus01337/attempt-at-xxh-prerun-plugin-nvm
Unknown package type: https://github.com/cyrus01337/attempt-at-xxh-prerun-plugin-nvm
xxh +I xxh-prerun-plugin-nvm+path+~/Desktop/projects/attempt-at-xxh-prerun-plugin-nvm
Unknown package type: xxh-prerun-plugin-nvm+path+~/Desktop/projects/attempt-at-xxh-prerun-plugin-nvm Did check the docs but may have missed something, the project hasn't even lifted off the ground yet. What are the prerequisites necessary in order for xxh to register my repo as a valid package? Here is the repo in question. |
hi @cyrus01337! Just remove |
Local OS (where xxh is installed): Ubuntu 20.04
Destination host OS: Ubuntu 20.04
xxh version: xxh/0.8.10
xxh-plugins installed: xxh-shell-zsh, xxh-plugin-zsh-ohmyzsh
Steps to Reproduce
On the host machine, try to use
npm
,yarn
,nvm
or any command that relies on it'sbin/
being present in$PATH
.zsh
will be unable to find the command and outputzsh: command not found: foo
- when running an installed application as a user with sufficient permissions from the host, it is expected to pick it up.I'm assuming
$PATH
is not carried over for security reasons/to prevent jank, there's also the possibility that this may be azsh
issue and am unsure if my mentioning such commands working on the host'szsh
nets any favourable insight. Have not tested on other shells.For community:
⬇️ Please click the 👍 reaction instead of leaving a
+1
or 👍 commentThe text was updated successfully, but these errors were encountered: