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
update node.js version beyond 10 #272
Comments
Cameron mentioned that we may be able to turn off building npm when we build node |
Is this anywhere on the near roadmap? v14 has been active LTS for several months now and the current version will be EOL within a month. Of course there are also several nice features and capabilities in the newer versions that would be nice to be able to use. |
there you go @sbowler ... on the near roadmap, now! do we have opinions on whether we should move straight from v10 to v14, or first go to v12? are we going to run into issues with either update (to v12 or v14)? should addons build without any changes, etc? @cameronfrandsen |
Thanks. I don't see any reason not to try to go straight to v14. Not sure what issues there might be. If anything I would expect issues with the addons. It would be really nice if someone could update them to use the new NAPI stuff and then updates would be less of an issue. Not sure who has time and could do that though. |
I have had my eye on v16. It comes out in April and it could potentially solve our FIPS compliance problems. |
only visual studio 2017 is supported by node v10.x (the latest is v10.24.1 as of right now) visual studio 2017 and 2019 are supported by node v12.x (latest is v12.22.1 as of right now) the latest node v14.x is currently v14.16.1
node v14.16.1 uses openssl 1.1.1k https://github.com/nodejs/node/tree/v14.16.1/deps/openssl nodejs/node@6bc8f58 |
latest node v14.x is currently v14.17.0 |
we currently patch v10.17.0 the patch is discussed here #219 (comment) |
building on Windows with Visual Studio 2019
|
Note: vcbuild no longer signs by default. "nosign" is redundant. issue #272
nodejs 14.17.0 fails to build with Visual Studio 2017
|
as part of the build of nodejs, headers are copied externpro/projects/nodejs.cmake Lines 114 to 131 in 25b462e
it appears that additional header(s) need to be copied with updated nodejs
|
project using node 14.17.0
I found an issue in another project that details "v8/node deprecated APIs and how to handle them" bcoin-org/bcrypto#7 -- their solution uses |
We'd be better off using NAPI. We already have that one, but it would take a lot of effort to do that. I can probably just go through these and fix them on a case by case basis. |
latest node v14.x is currently v14.17.6 (2021.08.31) node v14.17.6 uses openssl 1.1.1l |
completed with commits referenced above |
we currently build node version 10.17.0
https://github.com/smanders/externpro/blob/20.02.1/projects/node_10.17.0.cmake#L1
https://nodejs.org/en/about/releases/
with v10 there is an "intermittent linux build" failure "due to mulitple threads trying to access the cache", which slows down linux builds of VANTAGE webclient, but hopefully only a temporary slowdown until we move to a newer node version (VantageSuper/pull/4095)
The text was updated successfully, but these errors were encountered: