Maël Nison
Maël Nison
I got Yarn [working](https://xnfvye-5173.csb.app/), but the following warning messes with the output: ``` "OutgoingMessage#setTimeout" is not yet implemented. Please file an issue on GitHub. ```
I have the same issue with another ESM bundler, and it's quite difficult to figure out what happens. In my case it seems that DayGridView is passed to the `customGenerator`...
I don't repro; I suspect it comes from your side.
I'd tend to see the following: ## Filesystem access _(👎 out of scope)_ Node already has primitives allowing to access the filesystem, so the native archive implementation shouldn't open/write files...
I started a prototype implementation over at https://github.com/nodejs/node/pull/45651
I understand the general concern, and I wouldn't want to increase the Node.js surface if the value wasn't well identified. But while some modules can happen in userland, I think...
> This can, again, be said about everything that's best implemented as a native C++ addon right now. Native addons are a burden, and WebAssembly can be a meaningful alternative,...
> I believe the original reason for adding a zlib binding was for the purposes of compressing HTTP responses, not just for the sake of having common compression formats available....
SEA-related experiments are a use case, not the use case. This issue is about the general need, not an Node.js-internal one.
I still want to bring it to the finish line; last blocker so far is a memory leak reported by Asan which I found difficult to investigate. I'll make another...