Skip to content
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

[question] Global usage of a build package? #35

Open
hron84 opened this issue Aug 23, 2024 · 0 comments
Open

[question] Global usage of a build package? #35

hron84 opened this issue Aug 23, 2024 · 0 comments

Comments

@hron84
Copy link

hron84 commented Aug 23, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant