You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Copilot for Azure extension is MASSIVE in terms of what it should be on the local device. 350MB, and a large portion of this is the installation of node modules and languages that are for other platforms. I'm running windows 11 on intel, and I see that in the extension installation folder, there's a linux-x64, osx-arm64, osx-x64, win-arm64 in the node_modules section of the folder. All of these are wasted on my platform.
To combat extension bloat, either a single cross platform node_modules distribution should be created or somehow the extension should utilize the local node installation.
Alternatives and Workarounds
No response
Impact
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Thanks for the issue @johnwildes! We are aware of the massive extension size and do intend on addressing it. We'll leave this issue open as a place to give any updates on those efforts.
Problem
The Copilot for Azure extension is MASSIVE in terms of what it should be on the local device. 350MB, and a large portion of this is the installation of node modules and languages that are for other platforms. I'm running windows 11 on intel, and I see that in the extension installation folder, there's a linux-x64, osx-arm64, osx-x64, win-arm64 in the node_modules section of the folder. All of these are wasted on my platform.
C:\Users%USERNAME%.vscode-insiders\extensions\ms-azuretools.vscode-azure-github-copilot-0.3.97\dist\node_modules\microsoft.azure.copilotforazure.aiservice.webapi.localpackage
Desired Solution
To combat extension bloat, either a single cross platform node_modules distribution should be created or somehow the extension should utilize the local node installation.
Alternatives and Workarounds
No response
Impact
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: