Skip to content


sax stream behavior when piped a read stream which emits no data #67

kongelaks opened this Issue · 0 comments

1 participant


I'm just wondering what you think should happen in this scenario. Currently, it seems like the sax stream emits both 'error' and 'end' events when given a read stream which emits no data. I'm piping an http response to the sax stream and occasionally the response emits no data. When this happens, the sax event listeners end up calling my callback twice. I ended up just adding in a little check to see if 'error' had been emitted before calling my callback in 'end'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.