-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(#534): platform specific builds of vsix #612
base: development
Are you sure you want to change the base?
Conversation
> With respect to the failing CI, I recommend removing that workflow and using GitHub Projects's native way of automatically adding issues to projects. That can be done in a separate PR though. I think @kanej added it. I'm happy to remove it if you don't think it is useful anymore? _Originally posted by @OmarTawfik in NomicFoundation#598 (comment)
Hello. Changing the name and link to the social network in the documentation
0120264
to
c4cd326
Compare
@gordon-to Apologize for the long delay. Could you explain why we need platform-specific vsix files? we always distributed a single package through the vscode marketplace that should work on all supported platforms. |
It reduces download size for each platform and there are native bindings in this exension. Slang should also fix its package.json so that these dependencies are only installed on the correct cpu/arch 2.3M ./@nomicfoundation/slang-linux-arm64-gnu |
Thanks for the contribution. We are about to release a new version that uses Slang 0.19 (check this PR) , which uses wasm instead of native extensions, so the package size will be greatly reduced. We can revisit this PR after the upgrade |
Create platform specific vsix builds. closes #534.
vsce package
commandbased on https://github.com/microsoft/vscode-platform-specific-sample/blob/main/.github/workflows/ci.yml