uv tool install almost 6 GB?

[deas]

Hi,

did a uv tool install vectorcode.

Folder ~/.local/share/uv/tools/vectorcode is almost 6GB. Don't know much about it, but somehow feel I don't need the vast majority of the things installed for basic usage?

Is there are way to make it a bit lighter? ;)

[Davidyz]

This is most likely because Torch packs a bunch of Nvidia dependencies. They provide hardware acceleration for embedding/reranking models on supported GPUs. If you don't have cuda or is okay with the CPU-only performance for embedding and reranking, changing the index URL for torch so that it installs the cpu-only build should help. You can find the corresponding index URL on torch's website.

The docs contain instructions to do this for pipx, but I'm not quite sure whether the same env vars work for uv.

[deas]

Thanks, @Davidyz , that shaved over 4GB for me using pipx instead. The very same environment variables did not do the trick for me using uv.

PS: Feeling a bit embarrassed missing the bits in the docs.

[Davidyz]

No worries. I'm pretty sure there's an equivalent for uv too, it's just you might need to dig into their documentation.

I've also been looking into possibilities to publish with cpu-only torch and have cuda-enabled torch as an optional dependency, but I haven't had any luck because the only way to do this seems to be overwrite the index URL for the whole package, which is just not very elegant and may break for people who uses pypi mirrors.

[Davidyz]

I decided to change the suggested installation method to uv tool in #167 (bc it's so damn fast 🤣 ). Feel free to take a look and see if I'm missing anything.

[Davidyz]

That's curious. I tried using the --upgrade flag for a clean install, and it worked fine.

[deas]

Just to make sure we are on the same page :)

The build = ... nvim config mentioned appears to work fine once VectorCode is installed from the shell using the very same uv tool install --upgrade ... call. When not installed, I get "VectorCode CLI is not executable" - it looks like nvim checks for existence before it kicks off the build config. Wouldn't it make sense to always kick off the build config and potentially get away without ever worrying about installing VectorCode from a shell?

[Davidyz]

The build = ... nvim config mentioned appears to work fine once VectorCode is installed from the shell using the very same uv tool install --upgrade ... call. When not installed, I get "VectorCode CLI is not executable"

I tried uninstalling vectorcode and set build = 'uv tool install --upgrade "vectorcode[lsp,mcp]"', and it installed the CLI for me just fine. I'm on the latest release of uv (0.7.9). I'm not sure whether that matters.

Wouldn't it make sense to always kick off the build config and potentially get away without ever worrying about installing VectorCode from a shell?

tbh I don't think this is a big issue: the first time you use VectorCode would be in the terminal anyway (vectorcode init or vectorcode vectorise).

[deas]

Ok, got it.

Being new to nvim, I missed that build is a lazyvim prop and not vectorcode specific. Lazyvim kicks it off on install and upgrade. I removed the uv tool using the shell while keeping the plugin installed. That's why I ran into "VectorCode CLI is not executable".

[Davidyz]

Ah yes. The build command only runs on plugin installation/upgrade. You can manually trigger it by running :Lazy build VectorCode.