Unrelated - compiling recent Node.js for Win7

[tmcdos]

@win32ss
Since there is no private messaging on Github, I am posting here.
Do you by any chance have an idea how a Node.js version which is more recent than v16.6.2 can be compiled to run in Win7?
One of the problems is that recent versions of libuv rely on a WinAPI function GetHostnameW which is not available in Win7.
I found a patch for this but there could be other obstacles.
libuv_win7_GetHostnameW.patch

I tried once in the past to compile Node.js v14.x myself on a VM with stripped-down Win10 but I faced a lot of compiler errors.
I wonder can we try to keep recent Node.js (either fork or a list of patches - for as long as possible) runnable under Win7?

[win32ss]

I see here that this user has claimed to wait for version 20 to compile version 18 for Windows 7: https://github.com/vladimir-andreevich/node.js-windows-7

I will not be able to do this anytime soon due to time constraints, but I think a port would be relatively simple if the newer dependencies can be removed, as identified with Dependency Walker and any commits that specifically reference removal of legacy support.

Another problem is that node.js packages are in the form of Portable Executables. Ultimately all of the incompatible packages would need to be rebuilt or a reliable patcher would be needed to apply to them all (I am making a patcher for several Supermium components that are proprietary and downloaded by the browser, such as SODA - it could be applied to any other application as well).

[tmcdos]

Thank you very much, I was not aware of this repository! I will closely watch it from now on.
I am not sure which are these node.js packages you refer to be Portable Executables - as far as I am concerned, I only need the node.exe, everything else that is required in my daily job of web developer are NPM packages in pure JavaScript.

Regarding a patcher - I know about a guy who patches some DLLs to allow Chrome running on Win7: https://github.com/Blaukovitch/GOOGLE_CHROME_Windows_7_CRACK