deno remove/uninstall subcommand

[mhvsa]

We've got deno install and it would be convenient to also have deno remove or deno uninstall subcommand

[bartlomieju]

We had uninstall but removed it
https://github.com/denoland/deno_std/pull/512#issuecomment-504005054

[mhvsa]

oh, thank you

for myself rm $(which foo) works but I think it made sense to keep the uninstall

closing

[roc]

Just landed in deno land and I was absolutely baffled there's no uninstall or rm command! Is the reason that you expect a single location for something to be installed, a single version as well? I find it confusing to have an API that has a way of adding something but not of removing it.

[willgm]

@mhvsa

for myself rm $(which foo) works but I think it made sense to keep the uninstall

What about Windows users? Much of the Deno users may not know enough of his system terminal to remove it, and in the end feel lost about it.

I believe Deno should have a command to undo something that his own command have made.

[Yamboy1]

Even as a linux user I would prefer a specific command to do this rather than having to mess around with shell expansions and the such

[nateshmbhat]

oh, thank you

for myself rm $(which foo) works but I think it made sense to keep the uninstall

closing

The issue with rm $(which foo) is that , people can have other binaries than the ones from deno that have the same name as deno binaries. This can happen when the DENO path is suffixed to the system PATH instead of "prefixing".

So we need a deno uninstall command that will only look in the DENO path and remove the required files

[llluuulll]

hi,
so what command i can use to uninstall Deno ? i am on wondows 10 and i am not at all confortable with complet unknow commands, i dont understand.

rm $(witch foo), what is it wich foo ?
can some one point me the correct typo command to use ?

thx.

[ry]

The issue with rm $(which foo) is that , people can have other binaries than the ones from deno that have the same name as deno binaries. This can happen when the DENO path is suffixed to the system PATH instead of "prefixing".

Thanks - good argument.

I'm ok with something like this:

deno install --delete foo

[stefnotch]

I'd absolutely prefer deno uninstall over adding a delete flag to an install command. The latter seems like a odd hack and is going to cause a lot of googling and confusion for newcomers.

[lem0nify]

Return uninstall subcommand!

deno uninstall foo is much more elegant than navigating to and removing the script by hand!

[trivikr]

I agree that uninstall is a better option, as it's opposite of install - similar to npm install and npm uninstall

The command remove is opposite of add - similar to yarn add and yarn remove
The command delete is antonym of insert - similar to insertion and deletion in data structures.

deno uninstall should be preferred opposite for deno install

[whatevergeek]

i guess while this is still on discussion, we'll have to manage this manually by deciding which ones to delete under the deno folder.
e.g. on Windows 10, C:\Users\\AppData\Localdeno

[lem0nify]

@whatevergeek C:/Users/USERNAME/.deno/bin, IIRC.
But it's still not the most comfortable place to navigate.

Of course, uninstall subcommand is mostly needed in Windows, because Windows users are used to navigate and manage files with Explorer. By default, there is not even a shortcut to the home folder in Windows 10 Explorer and files/folders starting with dot are hidden. Of course, I know I can create my own shortcut and change file hiding policy, but it's weird and unnaturally that deno forces me do it instead of providing a way to uninstall with one simple command what was installed with one simple command.

To be honest, I do not see any objective reason to remove the uninstall subcommand, even if it seemed to someone unnecessary. How could its presence interfere to someone?

[llluuulll]

i am totally agee with @lem0nify
his comment resume perfectly the point

[wyrd-code]

I agree, this is an issue for me as well.

Take this case for example, I previously installed denon to use local development with a watcher. Now that Deno supports --watch, I upgraded and denon stopped working. Then I tried to upgrade the denon script but I don't see any commands to do that anywhere. After I realized I need to remove it manually (sic), I did a rm -rf ~/.deno/bin/denon. Trying to install it again now fails and I seem to be stuck with a message "error: No such file or directory (os error 2)".

If you remove a command like uninstall, the least you can do is refer to it in documentation, explaining why it was removed and how to handle the use case manually.

[David-Else]

This seems crazy! Where is the uninstall command?

[ChoqueCastroLD]

An uninstall command is the most intuitive thing to do instead of a flag

It will help a lot of newcomers to deno and people who are not so familiarized with their own terminal (windows users mostly)