Closed davisjam closed 4 years ago
Hi ! As you noticed, ezPAARSE downloads nvm
and the node version found in config.json
on build, and it will use the global installation of node only if it matches the required version. You can change the node version by modifying config.json
and run make
, however it may not work as expected. As of now ezPAARSE won't start under node v10+ for a reason that is yet to be investigated.
As of now ezPAARSE won't start under node v10+ for a reason that is yet to be investigated.
Understood. Is there an issue open with a description of the failure? I don't see one?
FYI I'm asking because I'm pondering using ezPAARSE as a benchmark for the nodejs/benchmarking runs. In that context it would be useful if it worked on LTS or development versions of Node. See this issue and this PR if you'd like to chime in, correct any misunderstandings I have, etc.
Actually there was no dedicated issue for this yet, as most of our users don't need to bother with version compatibility since ezPAARSE ships with its own node version. However we should get this fixed, so I created #77 and will get it fixed by the end of the week.
This project downloads nvm (?) and uses node v8.6.0.
Is this a hard dependency, or can it run on more recent versions of node? If it will work on more recent versions of node, how to configure this?
I see relevant-looking stuff in
config.json
andbin/buildnode
but would appreciate advice.