Latest Version of nwjs supported

[jpcharlesworth]

I recently successfully built node-sqlite3 for nwjs version 0.14.7 LTS but failed with the then latest version 0.17.6. Is there a way to find out the latest version of nwjs supported without having to go through the complex process of trying to build for it?

[Mithgol]

It's possible to start providing custom NW.js builds of node-sqlite3 if the result of #252 is reassembled (from its current remnants) over the limitations introduced on Travis CI by the migration from their old infrastructure to their new container-based infrastructure.

That migration allowed builds to start much faster and also to run faster (that's why node-sqlite3 opted in), but the newer infrastructure does not allow sudo. It brings the following problems:

• Installing the missing dependencies (about 20 APT packages) necessary for NW.js to run in Linux 32-bit mode. Currently we are rootless and therefore installing packages on the container-based infrastructure adheres to a whitelist. I haven't yet checked whether those 20 are all whitelisted.
• Running a headless NW.js to perform tests. The code of Build node-sqlite3 for node-webkit on Travis CI #252 used X Virtual Framebuffer for that. I haven't yet checked if the new infrastructure supports it. Might wait for the decision at headless version nwjs/nw.js#769 (comment) and see if it's positive.
• Performing 32-bit builds of node-sqlite3 (both for NW.js and for Node.js, which is currently disabled as well). Not sure if doable. If it's a dead end, then we might as well build in a Docker container running a 32-bit system (as recommended in 32 bit versions of linux images travis-ci/travis-ci#5770 (comment) once). Which also would mean having sudo inside the container (it's nice) but it might require sudo outside (as seen in Automating binary attachments to release. andlabs/libui#157 and in Travis CI docs, though the example at 32 bit versions of linux images travis-ci/travis-ci#5770 (comment) does not imply it) which would kinda defeat the purpose because the container-based infrastructure does not provide sudo.

[daniellockyer]

Would you be able to try with v5.0.3? 🙂