If I understand it correctly, it exchanges execution speed (by not using JIT) for faster starts. Instead, they could pick up the old FB project https://prepack.io/ to optimize both start AND execution speed. It would be very interesting to see it together with node's snapshots: https://blog.logrocket.com/snapshot-flags-node-js-v18-8/, which reduces the start significantly. - Source: Hacker News / 4 months ago

For those uninitiated, Prepack was a neat JavaScript code optimizer. It eliminated computations that could be done at compile time. https://prepack.io/ The project has been dead for quite a while, but it has valid use cases to this day. Source: over 1 year ago

Surely this is the job for something like https://prepack.io/. Source: almost 2 years ago

Some real examples in JavaScript can be seen on Prepack[2]. Consequently it is natural to wonder whether we can AOT compile components of client side frameworks, to achieve a reduction in the final bundle size, but also to increase application execution speed. Source: over 2 years ago

Default Artistic Style (astyle), https://astyle.sourceforge.net/ , is a pretty good one. Big thing for me is always "default", because it also means there is no need to configure every new environment. Source: over 1 year ago

Check out artistic style, which gives you pretty granular control over how everything is formatted. I don’t know if it’ll do exactly what you want, but in my experience it’s been a reliable formatting tool. Source: about 3 years ago