Charlike Mike Reagent
Charlike Mike Reagent
@mxschmitt yeah, types are messy, just assert it as http.IncomingMessage. We are not touching anything special except req.headers (and body of course) so it's basically working. In fact, that's the...
duh.. weird nodejs 😁🤦♂️ so it still doesn't make req.headers a fricking Headers? You can manually patch that temporarily. something like ```ts parseMultipartRequest({ body: req.body, headers: new Headers(req.headers) }) ```
@rdubois-crypto dang, it doesn't work for me. i'm planning to use `vm.etch` and Daimo's p256verifier? That should work right? :D
@nicolo-ribaudo haha, good catch. yeah, we should check just anything up to the `;`
Yup. Easiest fix is updating L16 to `this._map = Object.create(null);` this way later when you are accessing `this._map[key]` (in lot of places) you won't have problems such as with `constructor`....
@joshjung cool, thanks. I can do it in coming days.
@boustanihani heya you should be able to pass request-like object that has a binary `req.body` and `req.headers` (nodejs like headers, i think object) that would be a lot easier and...
There's no "workaround". If you simply want to rely ONLY on `setup-bun` it's not possible. The `bunx npm publish` does not work. It fails with `ENEEDAUTH`. I have been playing...