Export stream interface for browsers (esm)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 4.3k
- Forks
- 299
- Avg merge
- 16h 19m
- Merged PRs (30d)
- 1
Description
Summary
From what i can gather from #444 and the exported types in dist/esm/stream there is in theory a working implementation for web streams.
However there seems to be no /stream export for esm and parse imported from csv-parse/browser/esm does not return an object that would be usable as TranformStream.
Could you export the webstream variant for esm?
Motivation
I would like to be able use the same csv parsing library in both backend and frontend in order to minimize issues caused by differences in parsing behaviour.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the existing web-stream implementation and exported types under dist/esm/stream with the csv-parse/browser/esm entry point, and review issue #444 for context. Done means the ESM browser package exposes the web-stream variant and parse returns a usable TransformStream-compatible object.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api, web-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100