Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

response events eventually stop.

Open
#18 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
web-dev

Research direction

Use the linked gist as the reproduction, first disabling its JSON parsing lines as described. Compare response chunk events in Firefox and Chrome, watching for events that stop, the final-read exception, or thousands of zero-length chunks. Done means the streaming response continues delivering data without those failures.

Written by the indexing model from the issue text.

Description

I've been testing streaming JSON parsing and i ran in to this bug.

https://gist.github.com/mikeal/5471142

If you comment out the json parsing lines (those fail earlier than this bug surfaces due to a jsonstream bug, you can watch the length of all the chunks that get emitted.

In Firefox these events eventually stop and if you kill the server you'll get an exception when trying to read the last of the data.

In Chrome you'll eventually stop getting chunks with any data in them and it'll emit thousands of zero length chunks.

Dominant language
JavaScript
Stars
245
Forks
104
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from browserify/http-browserify

All issues in browserify/http-browserify

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.