[🐞] use native streams when available
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 22.1k
- Forks
- 1.4k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 52
Description
Which component is affected?
Qwik Runtime
Describe the bug
For SSR we're using a webstream, even on Node.js, and the implementation in Node.js doesn't cope well with many small strings being written.
We should use native streams when available.
Reproduction
n/a
Steps to reproduce
look at allocations recording in nodejs vs in browser
System Info
Node.js all versions
Additional Information
No response
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 in the Qwik Runtime SSR stream implementation and compare how streams are created for Node.js versus the browser. Use Node.js allocation recordings as the baseline, and consider the work complete when native streams are used where available without regressing browser streaming behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100