Hey folks! I thought I’d share a JavaScript parser I’ve been working on: https://github.com/thegreatercurve/okapi Very much a work-in-progress, but it's nearly fully compliant with the ECMAScript 2024 spec, 100% passes the Test262 parser test suite, and outputs ESTree. My next step is to look into refactoring it to output bytecode by default, with the hopes of turning that into an actual JS engine one day.

I have less need for this now after ending my tenure at a company that partially focused on code analysis, but... I am really glad there are now more options for JS analysis outside of the JS ecosystem for efficiency and sanity's sake. 🙏 Best of luck with the engine work 🤞 I wonder, is there a specific niche you're aiming to fill compared to the super optimized behemoths or is it more of a learning exercise?

@Dominik Jančík Definitely more of a learning experience atm, but I think there is a potential niche to build something similar to Quick.js, which only supports a subset of the spec and doesn't have a JIT, but is great for embedded or serverless usecases where fast start up times are a top priority.