Why does the packageing take sooo long?

[PraveenAsh]

I triggered a build for gulp packaging. It took forever!

npm run gulp vscode-win32-x64

[20:45:24] Starting 'vscode-win32-x64'...
[20:45:24] Starting clean-out-build ...
[20:45:24] Finished clean-out-build after 20 ms
[20:45:24] Starting build-date-file ...
[20:45:24] Finished build-date-file after 3 ms
[20:45:24] Starting compile-api-proposal-names ...
[20:45:24] Starting compilation api-proposal-names...
[20:45:24] Finished compilation api-proposal-names with 0 errors after 127 ms
[20:45:24] Finished compile-api-proposal-names after 143 ms
[20:45:24] Starting compile-src ...
[20:45:41] [mangler] Done collecting. Classes: 8129. Exported symbols: 9886
[20:45:48] [mangler] Done creating class replacements
[20:45:48] [mangler] Starting prepare rename edits
[20:45:49] Starting compilation...

I doesn't give any verbose or any compilation log

OS: Windows 10, 64 bit
Node version 20(but same result in other versions as well)
Build: Triggered locally using npm run gulp <variant>

[andrewpareles]

Bundling takes ~25 minutes on Mac, and Windows tends to be much slower. Unfortunately I think we're stuck with this for now since it comes with the vscode repo.

I recommend building instead of bundling right now! Void changes a lot day to day.

[PraveenAsh]

I use the build and debugger method to run it locally. But wanted share it with my beta users. How do I do it without spending 4hrs of time?

Is there a cloud alternative solution? Like building it on EC2 and dumping the installable like .exe file in S3?
I'm guessing vscode has a CI/CD pipeline to this. If so, could point me to some reading material or links or code?