Ben Noordhuis

Environment variables have the problem that they may not get propagated to child processes. Ex. `child_process.fork()`.

Blocked on https://github.com/nodejs/llhttp/issues/11 and a duplicate of several existing issues in this bug tracker (although none open at the moment, it seems.)

Thanks for the bug report. This is indeed different from #32463. I'm fairly sure it's a bug in the version of V8 that ships with node v16.x. v18.x should be...

> Even though It was fixed in v8/v8@fcdf35e, but we still got these errors. You're using v16.x, right? The fix isn't in any v16.x release. Try removing those two modules...

As expectation management: I don't know if this can be fixed in v16. I can't reproduce the bug myself, there is nothing that stands out when reading the relevant code...

@rapaktech Right here. :-) Node's tzdata comes from ICU. ICU's [binary data file](https://github.com/unicode-org/icu/releases/download/release-71-1/icu4c-71_1-data-bin-l.zip) is stored in [deps/icu-small/source/data/in](https://github.com/nodejs/node/tree/a1653ac71507d2db54632c09183428bb57ad9f52/deps/icu-small/source/data/in). Somehow that file should be updated to include newer tzdata - maybe by...

More details please? If you want to see your feature request accepted, outline when and where you would use the new functionality and what you think the API should look...

http2 is an argument against being too eager to absorb protocols into core. Neither its API nor its implementation are all that great; it would have benefited from iterating outside...

That's not true. Core has more supporting infrastructure for new code to piggyback on but there is little that you can't also do from a native module. n-api was a...

@mcollina The salient point is that n-api was available as a npm module before it got built into core and that was what allowed it to collect feedback and move...