Vincent Weevers

Same question as in #19: what can node core do better than userland? I'm not opposed, but I do think node core can aim higher than "users won't have to...

Happens because `sock.readable` is initially false (before `connect` has been emitted) and this branch is hit: https://github.com/nodejs/readable-stream/blob/49a45a92f4ccacd6ab496c5b5143b117bea2fa8b/lib/internal/streams/end-of-stream.js#L192-L197 Which evaluates to: ```js if ( !false && (!false || true) && (false...

Please welcome @prebuild-ci 👋

Note: no longer relevant since https://github.com/prebuild/prebuild-install/pull/149, so this issue is now about cleaning up that `prebuild-ci` account we never ended up using :) As well as leftover webhooks etc.

PR is welcome. I'm assuming it would be a few lines of code, reading something like `process.env.npm_config_cafile` and passing it to the request.

Thanks for taking the initiative. Note that in the context of `prebuild-install`, the fork doesn't fix known bugs and `rc` has no open vulnerabilities. I'm aware though of [GHSA-g2q5-5433-rhrf](https://github.com/advisories/GHSA-g2q5-5433-rhrf). I...

On second thought, it might make more sense to do this (i.e. deciding the initial unref/reffed state) in `level-party`.

As well as `NPM_CONFIG_BUILD_FROM_SOURCE=true` and `NPM_CONFIG_BUILD_FROM_SOURCE=` in the env.

> ``` > |-- build > |-- Release > |-- argon2.node > |-- leveldown.node > ``` A flat structure like that is ill-advised in any case, because some native modules...

Could this be solved with a webpack plugin, perhaps? That rewrites `require('node-gyp-build')(..)` calls.