Package standalone binaries via @vercel/pkg#343
Package standalone binaries via @vercel/pkg#343trxcllnt wants to merge 40 commits intodevcontainers:mainfrom
Conversation
161ec7b to
4e92744
Compare
|
@trxcllnt Any updates on this? |
|
@IgnisDa From my perspective this PR is complete (especially if the maintainers are comfortable w/ merging in the additional workflow changes in this branch). I'm just waiting on maintainer reviews/approval to run the CI jobs. |
|
@IgnisDa I don't know the right people to @ for attention, but feel free to comment if you do. |
|
Unfortunately, neither do I, but thanks for your work! |
…, create github release
|
Any news here? This would still be very very useful in many cases. |
|
Very interested in an official standalone binary. Also, noticed the vercel/pkg repo was archived back in January of 2024. |
|
I thought about starting to port the CLI to golang to make it rather easy to have a standalone binary (even static linked) for all systems available. I am familiar with golang enough but lack some time to do it all by myself. I could setup the repo and create the initial structure and cli application with some very basic functionaliy and if some people would join, I guess we would have something available fairly quickly. |
This PR is an attempt to address #7 (comment).
Publishing a standalone
devcontainerbinary that can be installed into images/machines w/onodewould be super helpful.pkgcan't statically analyze dynamic require calls, so I use staticnode-ptyrequires when bundling for use w/pkg.pkgwarns about other dynamic requires (seemingly fromyargs), so we should validate these aren't executed at runtime.package-standalonenpm script to create standalone[win, linux] x [amd64, arm64]binarieslinux-x64andwin-x64tests 🎉I have a separate branch that adds macOS binaries and updates the GHA workflows to build/test/publish them. I've held off merging it into this PR because it's a huge change to
dev-containers.ymlandpublish-dev-containers.yml, but I can if folks are comfortable reviewing it all together.edit: I've updated the release action to create GH releases w/ the new artifacts (see this sample release).
edit 2: I've opened a draft PR with the workflow changes in #385