Replies: 1 comment
-
This is still a discussion. The issue tracker is for issues with the binary, not bug. The issue wasn't closed, it was moved and it is a "feature" that the original issue gets closed and the discussion opened. Either continue the conversation in that discussion, or continue it here, in this discussion. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Discussed in #12493
I get you folks closed the original issue and moved it to discussions. But I think I have a legitimate situation here and the response to the original issue didn't address what was in question or even clarify a mistake from my part.
I don't want to be rude or bully the project team, far from it. Just really trying to get myself out of a block.
This time I added a gif in attempt to better illustrate the case.
I'm trying to build a simple CLI tool to run dev scripts with Deno. The goal is to create cross-platform scripts with type safety.
I'm not succeeding with Deno.run(). I think this is due to part of my scripts are based on global packages installed with NPM like, for example, the firebase CLI tool.
If i run something like this:
I get this error
Here in live:
I found some clarification in this issue about echo. But, I'm afraid if I prefix everything with
"cmd", "/c",
the program will tie itself to the OS. Is this a valid assumption?Is there another API that enables us to run commands through the current shell instead of attempt to find binaries in the system directly?
I think in node this is done with something like this:
Thanks for the awesome tool.
JM
Beta Was this translation helpful? Give feedback.
All reactions