Isaiah Thomason

My main concern is similar to another issue that I recently opened; it relates to authentication. There are authentication-related packages (e.g., `SuperTokens`) that often need to return headers and cookies;...

@dummdidumm Just pinging in case this got missed. I saw the label so I didn't know if you were awaiting a ping or not.

Which headers they'd be setting, I'm not certain about. :confused: The `SuperTokens` codebase is a little difficult to dig around. But I did see that at times they set certain...

> The API is the way it is because setting the same header from different places is likely an error. Because multiple loads happen concurrently, it's potentially also non-deterministic. Yeah...

Yes. When I tried that, what I saw in the Network tab was something like ``` my-header: first value, second value ``` But when I used `Headers.append` I saw this...

Ah, okay cool. In that case yeah, just doing a `.join` works fine. Thanks again for the clarity and patience 🙏🏾

So from some of the use cases that I'm seeing (which also seem to coincide with some of mine), I'm wondering if what's _really_ coming out is a desire to...

@anuragmerndev I can't speak for RP, but in my opinion adding a new build system introduces additional complexity. This increases the risk for unexpected bugs, and it might cause your...

From the video, I can see that the build works; but I don't see the examples of ESM-based/CJS-based/TypeScript Node applications working properly. How did those go?

Also just giving a reminder to target the proper version branch, as mentioned in the PR checklist.