Skip to content

TextDecoder and Web streams #339

@bjohansebas

Description

@bjohansebas

Something I've been thinking about since I researched this package is that we could use web streams and TextDecoder for stream support in the browser. There's work done by Alexander (https://github.com/pillarjs/iconv-lite/tree/next) that uses the idea of backers to somewhat separate the logic between environments, which I think would be a great starting point. I haven’t explored this in depth yet.

We also need to remember that this package is used by body-parser, raw-body, and qs, among many others, so we can’t stop using Node.js streams, since those packages rely on Node.js streams. Some kind of logic would be needed to convert Node.js streams to web streams.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions