Espruino Build issues using README_BuildProcess.md and Extending+Espruino+1 within Windows10 environment

Mon 2019.10.07

Not being picky, but wanted to validate what I thought I saw for d/l options, as my belief was a .bin and a .hex for all builds.

https://www.espruino.com/Download
From the link 'You can also browse by Git commit hash'
http://www.espruino.com/binaries/travis/?C=M;O=D
The most current build 2v04 as of today:
http://www.espruino.com/binaries/travis/1a4f2864e3a15a60f91040ce2ad52e844c238fd8/

But, looking at Puck, an nRF52 for instance, actually is d/l as a .zip, containing a .bin and .dat but no .hex, so is there still a qualifier needed in your #9 sentence? I'm still way too new to have enough of an understanding to even make a feeble suggestion here.

Thank you @AkosLukacs for hanging in there to guide me to a solution. Still tons to learn, but at least I have the basics to dig through the 'C' source and make improvement suggestions. I have now successfully created my own Espruino Build!
With this limited knowledge however, . . . Watch Out, as I am now dangerous!!

I'll post some install tips for Win10 later this week.