Julian Gruber
Julian Gruber
Thanks, this has been fixed :) Do you have a plan for E2E tests?
Hashing will impose a _significant_ overhead. While more correct, we might still get better results with just "overwriting" with the identical, no?
I can't talk about what's going on, but please take note that this project has been deprecated https://github.com/hypercore-protocol/hyperdrive-daemon/blob/586389c2d1c1d1b222000f5866c6179c0a4253b2/README.md#hyperdrive-daemon, so you might find a replacement that works better
If you use `res.json()` for example, an error will be thrown once the internal stream has reached `opts.size` bytes. If you use `res.body`, for example like this: ```js res.body.pipe(fs.createWriteStream('./out.txt')) ```...
I'm solving this internally by replacing `res.body` with a stream that emits an error once `opts.size` bytes have been reached.
> I would say that this is obvious It wasn't obvious to me. I expected `res.body` to emit an `"error"` once `opts.size` bytes had been received. The default way of...
If it helps, here is my basic implementation: ```js class LimitStream extends Transform { constructor (limit) { super() this._bytesLimit = limit this._bytesWritten = 0 } _transform (chunk, _, cb) {...
Nice, thanks for sharing, this is a lot simpler using async iteration
works for me: use ``, then let webpack handle any relative requires
+1 if it's just for style props