Deno CLI Broken
Anytime I attempt to run the deno CLI the arrow keys get stuck and I cannot make a selection. I have tried this on two separate machines, so I know it's not an environment issue.
Here is the command I'm running:
Not sure what I can do here - i've been messing with it for a day now to no avail. Any suggestions? Anyone else experiencing the issue?
9 Replies
I wasn't able to find the answer to your question in the official Deno documentation. However, based on the command you've provided, I noticed that the syntax for using a third-party module from a URL or a package manager seems to be incorrect. In Deno, when you want to run a module directly from a URL, you typically specify the full URL to the script.
The command you're using seems to be attempting to use npm package syntax (
npm:<package>@<version>), which is not a standard Deno command or module specifier. Deno does not use npm packages directly; instead, it uses modules referenced by URLs.
If you're trying to run a third-party module, you should ensure that you're using a URL that points directly to the module's entry file. For example:
Replace https://example.com/mod.ts with the actual URL of the module you're trying to run.
Please note that this advice is not based on the Deno documentation, and I would advise you to double-check the accuracy of the advice given. If you continue to experience issues with the Deno CLI, you might want to reach out to the Deno community or check the GitHub issues for similar problems that other users might have reported.Nobody else having the problem?
aight, back to asp.net core 🙂 was excited to figure out how to get deno up and running
That sounds like a bug in Deno. Can you open an issue https://github.com/denoland/deno/issues/new/choose ?
@bbqchickenrobot which OS are you on? I think there's a problem on Windows that we are eyeballing to fix
yes, on windows - I can possibly try wsl ?
That should work, @divy was looking into that Windows big, it's really tricky to fix
Got it - ok cool thanks - i'll do that iv not, i'll spin up a linux vm and create it there and copy it back.
I did try it and it works fine with WSL, but not on Windows. Tried on git bash console and normal terminal
ya, same , got it up and running via WSL as well