FSM scope depth parser: Node.JS - Put in Desc When Done *Then back to VideoGame\JS dev 🤷‍♂️

Working on a Lexical Parser - That I will paste in the YouTube video desc when done, for anyone to use. (have to figure out which legal license I'll slap on it.. most ignore licenses (OpenAI, Anthropic, Microsuck, Google, etc) so, might just be free, I'll make $ off the JonsScript engine anyways, whatevs). + SHORT/SWEET SUMMARY: The JonsScript API expects a parsed representation rather than raw source code. I'm releasing the parser separately so it can produce the AST needed by the engine. Existing JavaScript engines generally integrate parsing and execution into the same runtime, whereas I want these components to be usable independently. AND THEN LONGER SUMMARY: I'm building a configurable parser that can read source code, as a separate layer, to understand nested structures like blocks and strings, produce an Abstract Syntax Tree, and feed that tree into my custom JonsScript execution engine (like JavaScript, literally will be 1st to 100% satisfy ECMA-262 standard spec fully(will stream it over way to many live streams, make a new YouTube play list for it, from page 1 of the spec, to the last page. literally. Be 1st to 100% meet the spec.), but its also all the things JS fundamentally lacks.. being why JavaScript will die/phase out, and JonsScript will take its place. lol, frfr. Or not, who knows. Idk. 😄), which is multiple times faster than the standard JavaScript engine (the JavaScript engine is 32bit in c language, I made it like 9 years ago, still need to finish converting it to 64bit, and re-write the thing to 64bit x86-64 and ARM64 assembly for Desktop, and Mobile.. streaming the process, need to get this done, to get back to that. lawl). ALSO LONGER SUMMARY EXTENDED: ... the JonsScript API will need things parsed, to spoon feed what goes into the JonsScript API for running it, because JavaScript is SLOW the parsing is COUPLED with the engine (So anyone could use the parser without using the engine, or use the engine with another parser).. and real performance has layers, like an onion, or an ogre, or your mom, few people make competent parsers so I have to release the top layer of a parser that can be used for freeeee. (The bottom layer the JS engine part.. have to finish that up.) If I release an advanced JavaScript API, called JonsScript, it will not replace JavaScript if nobody knows how to parse and fill out the API structure that runs it. So I'm making a Lexical/Scope Parser, and its a "Generic Parser"!! so it runs off a Grammar Table or [Object object] since its Node.JS ..meaning the parser will work with ANY syntax, as long as it fills out the Grammar Table, and output an AST tree (object of scopes, or leafs, or whatever), that can be traversed after to pick out and identify the Number/Labels/Tokens/Operations and such. So the (Block scope: { ThisIsABlock; }) or (String scope: "this is a string.") or the "[]" or "()" thats what the parser will resolve (along with correctly determine/omit scopes inside of a scope based on the kind of scope. so a string scope will be a string, if a "{}" is present that will be IGNORED in the AST a string scope, is a string), all the difficult stuff that is annoying to deal with when parsing things. (or it will parse for c language scopes, and such, if you modify the Grammar table.. after I get it done, and paste it here in the description.) ... Put The Lexical Parser Node.JS code HERE!! (when done, if it ends up more then 5000 letters.. I will have to put it on Github, or something. Idk, whatever, paste it somewhere when done.) FINALLY! ORIGINAL DESCRIPTION: (I need to make, separate playlist for things.. eghh.) [JonsScript] Eventually back to working on independent low level JS Assembler - Developing an ECMA-262 (then making a better standard with useful bells and whistles) compliant cross platform Desktop/Mobile engine that will actually utilize CPU's for high performance data processing/gaming via plain c language with some 64bit(and 32bit but platform wise only 64bit) x86_64/ARM64 assembly in the mix. (Un-unaliving a 32-bit Engine that took 2 years to create 7/8 years ago, updating to 64bit then release! The whole process TO GO. 🫃 ← like giving birth, but w/out the mucus plug.) That's it. Full Playlist| 🔴 https://www.youtube.com/live/aZY7xtBh...