From second view, looks like good way using ECMA-6 (for example) with Babel and some things added into browser debugger. So, technically, high-level ECMA-6 lan

From second view, looks like good way using ECMA-6 (for example) with Babel and some things added into browser debugger. So, technically, high-level ECMA-6 language transpiled (more traditional word translated) to ordinary Javascript, and supplied file with structures, similar ideologically to C symbols tables, and within browser debugger (Chrome work) you could see not target JS but sources and debug on high level. And when your code become mature, you just remove symbols tables and as usual, target optimized code become very much like obfuscated, and you could provide it as closed source. So, as summary - must have all from list: 1. high-level language translator (may be into assembler, may be into some lover level language, as with ECMA-6 and JS) 2. some sort of debug support (as mentioned symbols tables) 3. good enough debugger, as much close to client platform as possible (Chrome is good example).