Ruben Verborgh

> instead of having to wrap all other RDF-JS tools with a custom pre/post process step (kind of defeating the purpose of RDF-JS ;) Well well, let's not exaggerate 🙂...

> We'll probably settle on an option similar to this one, where we'll wrap the N3 parser interface and expose a stream with proper error handling. Great! Do let me...

Thanks @olebor, that makes sense. For backward compatibility, we could activate async support if either a `done` callback is passed as an argument or a promise is returned by the...

> To clarify: Since the lib itself calls the function, it would be the lib passing the `done` callback into it. We would then have to check if the function...

That shouldn't be the case indeed! Are you sure it's not an HTTP/HTTPS redirect issue as in https://github.com/follow-redirects/follow-redirects/issues/192?

It's on the backlog; current funds are too limited to put a dedicated person on this. I'm trying on a best-effort basis.

> * [This line](https://github.com/follow-redirects/follow-redirects/blob/35a517c5861d79dc8bff7db8626013d20b711b06/index.js#L456) calls `spreadUrlObject` but doesn't assign it to anything, making it effectively a no-op. It assigns it to the second parameter: https://github.com/follow-redirects/follow-redirects/blob/35a517c5861d79dc8bff7db8626013d20b711b06/index.js#L585 > * We might be...

Do check https://github.com/follow-redirects/follow-redirects/issues/261 as well.

Thanks, could you please provide code to reproduce?

Shall we first distill the problem we are addressing? Then we can look into various solutions. I’m not a big fan of the reason phrase, as this is no longer...