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
Confused Usage - Help About Node 18 Versions #1085
Comments
I had the same situation and still used the |
@vuquanganhnguyen @andre-mr I tried to use the
I have tried as the docs says to install the prerequisites, but got error, any suggestions thanks in advance.
|
Hi.
I tried to package my node app.js using pkg. it worked like a charm, using just "pkg ."
But i figured out that pkg uses Node 18.5 as last Node release available, and pkg was deprecated in January 2024.
Then i tried nexe, but all seems confusing to me:
Well. Node 18.18.0 is the version i'm using here, but I just didn't find where is stated that nexe will use current version other than download, or try to download a pre-build version exactly the same number i have in use.
From docs I see --target option but got confused about if those version numbers are about node or nexe specific builds.
It seems the latest for windows x64 is this:
windows-x64-14.15.3 - 53.9 MB - Jan 3, 2021
That 'releases' page is signed as "v3".
Is that version number a NodeJS version? Why so old? Don't we have any prebuild package using not deprecated Node versions like 18 or 20?
I see there is a build option where I need to prepare my system for a local build, and I wonder if that's the only workaround to use Node 18+ (18.18+ really) to build the exe.
I'm trying to use Node 18.18 or newer other than 18.5 available with pkg, because my app uses Fetch API and for node 18.5- every time it executes a 'experimental warning' is shown in terminal.
It could be node 20+ too.
Thanks for help.
The text was updated successfully, but these errors were encountered: