The copilot plugin is taking 1.6GB space in the ~/.config/nvim/lazy

[bidhovbizar]

I am using neovim 0.11.4 with lazy as my package manager. I use copilot along with copilotchat and codecompanion but the size of the plugin is increasing to a point that it has actually started to slow my pc down.

Is copilot supposed to take this much space especially compared other plugins which are less than 50mb? I have corporate server where my home doesn't allow more than 2 gb space and copilot takes 1.6 gb. This behaviour is seen across ubuntu, rhel.

(venv) bbizar@automationvm-59:~/.local/share/nvim/lazy/copilot.lua$ du -h --max-depth=1 .
8.0K ./.githooks
28K ./doc
8.0K ./plugin
436K ./tests
52K ./.github
580M ./.git
983M ./copilot
4.0K ./deps
276K ./lua
1.6G . <-

[haunt98]

Same here for me

❯ du -h -d 1 .
4.0K    ./.githooks
982M    ./copilot
412K    ./tests
4.0K    ./plugin
220K    ./lua
 40K    ./.github
  0B    ./deps
 24K    ./doc
344M    ./.git
1.3G    .

I use version v3.0.3

[AntoineGS]

Oh nice catch, I had not released, from what I can see the LSP is coming with a bunch of binaries.
I will see if there is anything I can trim out!

Edit: If all else fails the compiled binaries are smaller, it could be an option to create a branch without the js repo to use the binaries.

[AntoineGS]

So I was able to trim it down a bit, but due to the git history and the fact that the LSP is packaged with the sources, the .git folder is still pretty big.
If you would like to save more space, could you try changing your config to use the binary releases?
That feature is not used much so you may encounter some friction, but if it gets used I will take time to improve it.
If that works for you, then I can see if creating a new branch without the LSP and its history would work (I don't see why not).

[AntoineGS]

So the issue has gotten worst, newer upstream releases include a couple of 100mb+ binaries, which GitHub is refusing due to its 100mb size limit. So to release those I would need to include them zipped, and then unzip them, but this only postpones having to find a proper solution as the LSP repo keeps getting bigger. When I attempted to migrate to the binary releases last time the download was failing on some OSes, but I think that's the best solution moving forward. I'll try and see if I can dig up those issues and give it another go.
Maybe removing the LSP altogether from this project would be easier, and make it a 'bring your own LSP' 😂.
I am open to suggestions :)

[MunifTanjim]

I can't even clone this repo anymore 😐

[girirahayu]

is any update here ?? :D lol.. i regret to update my nvim

[MunifTanjim]

You can do git config --global http.postBuffer 524288000 to try and unblock yourself. But this repo needs to be cleaned up. It's borderline unusable right now.

[AntoineGS]

Quick update, I am working on improving the current binary download so it can become the default, and remove all traces of the LSP files from the main branch. This is the best long-term approach I could find but short-term it will likely be disruptive to some while I resolve OS-specific issues. Once I have something working I'll post here how to test-drive the new process, hopefully I can get some feedback before doing a full release.

[AntoineGS]

It is still a work in progress as I got the initial work up and running with ChatGPT Sol and have been reviewing/tweaking it since (it lovesss over-engineering solutions), but if anyone wants to give it a try the branch poc-remove-lsp can be used.
This does not include the scrubbing of the git history to reduce the size of the .git folder but does remove the LSP from the current commits, and downloads the binary (or node project) on-demand.
Feedback is appreciated as I work through it, last time I deployed a binary-first update I had to roll it back due to too many failures on less common OS setups.

[AntoineGS]

Has anyone tested the new branch? I will probably merge it within the next week since LSP updates have been broken and more users are encountering pull/clone issues.