How to manage global installed? (e.g., deno outdated --global)

[qupig]

I found this very confusing about how to manage global installed.

For install and uninstall, they worked:

deno install --global
deno uninstall --global

BUT

How do we list global installed?
How do we check outdated global installed? (The command does not accept --global param)

[shine-on-me]

Ever found anything for this?

[bricefriha]

Thanks @qupig for the workaround
It would be nice to have a command to actually list them, if I'm honest.

[shine-on-me]

Yea manually installing/uninstalling is what i've been doing indeed for the packages that work globally, too bad the --global install seems to be fairly limited (for now at least).

For example, installing sharp globally doesn't seem to work either, it keeps complaining about lifecycle scripts even though it's applied during install:

deno install -g -RWE --allow-ffi --node-modules-dir=auto --allow-scripts=npm:sharp npm:sharp

results in:

Warning The following packages contained npm lifecycle scripts (preinstall/install/postinstall) that were not executed:
npm:sharp@0.33.5
This may cause the packages to not work correctly
To run lifecycle scripts, use the --allow-scripts flag with deno install: deno install --allow-scripts=npm:sharp@0.33.5
✅ Successfully installed sharp

running sharp --version then gives:

error: Failed resolving binary export. /home/user/.cache/deno/npm/registry.npmjs.org/sharp/0.33.5/package.json did not have a bin property

According to the sharp devs the postinstall scripts aren't needed unless building from source, but deno doesn't seem to play along lol

[qupig]

@shine-on-me As far as I know, if the package does not have a bin entry, it cannot run even in the npm global installation.

[shine-on-me]

I see, I couldve sworn I managed to get the sharp globall install to work a while ago, maybe it was some older version but I don't remember how I did it.

For now as a backup I just use the sharp-cli package which does seem to work ;D

But same thing here, any updates will require a deno uninstall -g your_package first...

[qupig]

Just share. I think the most convenient and feasible way to do it at the moment is to maintain a local project.
In this project, import any libraries, alias or customize something you want to use and install the file globally.
Then any subsequent upgrades can then be performed in the project normally with deno outdated etc.

Refs:
Global installation
deno install --global [PACKAGE_OR_URL]

deno install --global --allow-net --allow-read --name mycli "/path/to/file/mycli.ts"
deno install -g -N -R -n mycli "/path/to/file/mycli.ts"

Tip

You must specify permissions that will be used to run the script at installation time.
For good practice, use the import.meta.main idiom to specify the entry point in an executable script.

[qupig]

Because of:

• deno outdated version detection error #29647

And deno outdated cannot detect updates of (npm, jsr, https) packages directly imported in the file at all.

In other words, deno outdated can only detect packages in deno.json, and there are still bugs in version checking.

I now think it's difficult to manage dependencies in Deno even with the above workaround.