Vinicius Lourenço

Currently, all the NodeJS (>10.x) applications that check for musl, use the `getReport`. > The approach that process.report.getReport() takes (check the system's dynamic linker) is... let's be diplomatic and call...

> To ask the question is to answer it, isn't it? :-) It can't be half-baked. If we agree that the current way of using `getReport` is accurate enough, we...

So, let's separate into two main problems: ## Expose libc version Those who want to get the information about the libc and the libraries that want to check if musl...

Since we couldn't come to a consensus on what approach we should take for this, I'll close this issue as I'm satisfied with solving this problem in userland with the...

+1, he is always helpful with Windows PRs.

He probably can, but I don't think it's worth the effort, as he probably has that if to be able to introduce new checks after `undefined value===`. But it's just...

@kamilmysliwiec I already did that with WeakMap, I describe that approach at https://github.com/nestjs/nest/issues/10844#issuecomment-1399282773 under `Using object reference as an ID`. But that approach breaks the serialization across multiple runs. >...

> 99,9% of users wouldn't ever make use of that simply because most framework users don't (and really shouldn't) care about how they're internally represented & orchestrated. I agree with...

@kamilmysliwiec From what I understand, we have some choices: - continue with the introduction of the API proposed in this PR - do what you mentioned about associating a [Symbol]...

@dbrxnds In theory, you just need to create an adapter for `Vercel`, in order to parse in/out the Request/Response. Create an issue on my Serverless Adapter repository with a minimal...