You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondered when I first ran into the YALC and then Knit if they support using the published "local" package as a global command. For example, I ran into an issue with deepl-translate-cli package and wanna try out one of their fork on my machine. Howver, since it is a CLI command written in NodeJS, I wanna use it globally from multiple (bash-based) projects rather than using it via NPM (so, I do not want to write some workarounds picking up commands from node_modules folder to every scripts, rather I wanna rely on the PATH variable).
Do you plan to support this use case? Or is there any way to use a package published by this stuff in global context (like, how it works with yarn global add foobar)?
I use NVM for Node locally, I really do not care about polluting my NodeJS context since I do not use anything for NodeJS development, rather I use CLI tools for Bash projects.
The text was updated successfully, but these errors were encountered:
I was wondered when I first ran into the YALC and then Knit if they support using the published "local" package as a global command. For example, I ran into an issue with
deepl-translate-cli
package and wanna try out one of their fork on my machine. Howver, since it is a CLI command written in NodeJS, I wanna use it globally from multiple (bash-based) projects rather than using it via NPM (so, I do not want to write some workarounds picking up commands fromnode_modules
folder to every scripts, rather I wanna rely on the PATH variable).Do you plan to support this use case? Or is there any way to use a package published by this stuff in global context (like, how it works with
yarn global add foobar
)?I use NVM for Node locally, I really do not care about polluting my NodeJS context since I do not use anything for NodeJS development, rather I use CLI tools for Bash projects.
The text was updated successfully, but these errors were encountered: