This repository has been archived by the owner on Feb 8, 2020. It is now read-only.
Testing building TS with pkg #1
Open
Conversation
This file contains 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I tried both
nexeandpkg. Had some problems withnexeignoring command line options (--target) and compiling node for 30minutes.pkgseems more robust and got the job done instantly.Building binary is fast, and works for all platforms, the downside is file size - ~35 MB on my machine for a hello world app and that was common for both solutions.
I believe we can somehow tune the process to reduce output size
(eg. https://github.com/upx/upx)