-
Notifications
You must be signed in to change notification settings - Fork 212
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
pixi run deno
just invokes pixi again
#2982
Comments
We use |
Hi there, knowing this was working in older versions of Pixi, I did a quick "binary search" to identify the issue was introduced in 0.39.3
works correctly
shows the pixi help
Hope this helps |
Thank you, that was the release we bumped |
This code is part of the issue: denoland/deno_task_shell#123 We'll check if we can make a work around. |
At [pixi](https://github.com/prefix-dev/pixi) we use the `deno_task_shell` in a very similar way as deno does. Like deno, `pixi` can manage packages, including deno. However, with the current setup `pixi run deno` leads to pixi being called rather than deno. Therefore, we'd appreciate if we could configure the executable name. This allows us to configure it like this in `config.toml`: ```toml [env] # Needed so that `pixi run deno`, calls deno instead of pixi DENO_EXECUTABLE_NAME = "pixi" ``` Related issue: prefix-dev/pixi#2982
Checks
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pixi, using
pixi --version
.Reproducible example
Issue description
It's not possible to run deno with
pixi run
directly, which is a real pain. I don't know why this is, but when adding a wrapper script it works again.This is the work around for me, but it would obviously be ideal if we could skip that step.
Expected behavior
For me to be able to just run
pixi run deno
without the wrapper.The text was updated successfully, but these errors were encountered: