Paulo Coghi

> 1. Write code to wrap each specific event that we want to support. > 2. Expose all events to the user so they can write platform-specific code if they...

For the reasons explained above, I vote to merge this. Adding tests for the new function on `webview_test.cc` would be good, but not strictly necessary on this stage, on my...

It would be interesting to generate a coverage report based on the `kcov` one* where the different logical possibilities and ramifications are informed in detail, as Jest does: _(informing the...

The (main) point here is not the executable size or the ability to "compile" javascript into machine code. The point here is the ability to create a single executable which...

Thanks to Dom (on Bun's Discord channel), that pointed me to [github.com/theseyan/bkg](https://github.com/theseyan/bkg). The @theseyan's strategy on **bkg** is very clean and it may be interesting in bring it into Bun...

@Slapbox, here is a table with binary sizes on Linux, using `bun build --compile ...` as well as [`bkg`](https://github.com/theseyan/bkg) and `pkg` (latest nodejs LTS, v18). The js source code is...

This can be closed :)

Is it possible to bypass this check and/or is there an option to already inform the contents of SAN?

What is the opinion of the maintainers on fanotify? It seems the next step. According to the fanotify's author ([here](https://lkml.org/lkml/2016/12/20/312)), it provides "the ability to set a single (fanotify) watch...

Could we check the kernel version or the existence of fanotify and use it when available?