-
Notifications
You must be signed in to change notification settings - Fork 66
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
Retire binary hlx distribution #696
Comments
stefan-guggisberg
added a commit
that referenced
this issue
Apr 2, 2019
stefan-guggisberg
added a commit
that referenced
this issue
Apr 2, 2019
resolved according to proposal |
@stefan-guggisberg I think this file is no longer needed, correct? |
stefan-guggisberg
added a commit
that referenced
this issue
Apr 9, 2019
fixed in de2c914 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview
Recent binary
hlx
releases are all broken. The last know to work release isv0.13.8
. See related issues:Details
The binary
hlx
executable is build using node-packer.node-packer
embedsNode 8.3
runtime within the native executable.As of #397 (0528466)
Node >=8.9
is required to run the CLI.OTOH the
node-packer
project is abandoned, the current release is 2 years old (bundlingNode 8.3
runtime). I forked the project and ported the runtime to8.15
and10.15
, only to run into new issues (e.g. #687, #689, failure to load native addons, etc). There are potentially a lot more issues. Fixing those issues would require a deep dive into v8, libuv, libsquash and Node core C/C++ code, hardly worth the effort.While there are other projects which create native executables from node apps (
pkg
,enclose
,nexe
,electron
etc) none of them work forhelix-cli
(lack of native addon support, no dynamic requires, etc).Proposed Actions
I suggest we stop providing binary
hlx
builds, at least until we find a viable solution.This would mean we remove any reference from READMEs, docs etc and remove the build job on CircleCi.
The text was updated successfully, but these errors were encountered: