build as plain js bundle without embedded bun#33
Open
ralphptorres wants to merge 2 commits into
Open
Conversation
allows building a plain js bundle without embedding the bun runtime, useful for distribution packaging where bun is a system dependency
ralphptorres
force-pushed
the
feat/build-bundle
branch
from
49a83a2 to
1ce0d15
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
bun build --compileembeds the bun runtime, producing a ~100 MB binary. this PR adds a--no-compileflag tobuild-cli.mjsand abuild:bundlescript that skips that, outputting a plainrelease/proton-drive.js(~a few MB) instead. useful for distros like arch linux that already ship bun and prefer system-managed runtimesbun run build:bundleis the resulting commandcallers are responsible for invoking the bundle with a wrapper:
exec bun /path/to/proton-drive.js "$@"